Shareware Overload Trio 2

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Overload Trio 2 / Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO / dir34 / katlog.zip / KATBOOK.OQT / katbook.out

Wrap

Text File | 1989-04-01 | 208KB | 4,137 lines

DBS-KAT (R) The Easy, Practical, Super Capacity Diskette Cataloger And Hard Disk Archive Utility USER MANUAL by R.H. Martin Applied Foresight Inc. P.O. Box 20607 Bloomington, Minn. 55420 April 1, 1989 Copyright 1986 by R.H. Martin All Rights Reserved A DB-ShareWare Software Product A limited license is hereby granted to copy and distribute wholly unmodified copies of the DBS-KAT Software Diskette which contains this manual (Read the manual, "THE DB-SHAREWARE PROGRAM" for full details about this limited license) (DBS-KAT was originally released under the name, PC-KAT) DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 2 TABLE OF CONTENTS ----------------- Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 General Trademarks Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Overview Philsophy Of DBS-KAT Using DBS-KAT With The IBM AT DBS-KAT Base System Features Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 Minimum Requirements Recommended Options Commentary Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Overview Installation Instructions Installation For Non-IBM Compatible MS-DOS PC Additional Install Information For Hard Disk Users Who Power On Their Computer With A Startup Diskette Updating The DBS-KAT System Control Record. . . . . . . . . . . . . . .13 Cataloging Diskettes. . . . . . . . . . . . . . . . . . . . . . . . . .21 Inquiring Against The DBS-KAT Catalog . . . . . . . . . . . . . . . . .26 Taking Care of Your Database. . . . . . . . . . . . . . . . . . . . . .30 Overview Conservative Updating Backup The Log File Integrity Analysis Trouble Shooting Tips . . . . . . . . . . . . . . . . . . . . . . . . .34 Online Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Appendix A: The KPRINT Print Program. . . . . . . . . . . . . . . . . .36 Appendix B: KATSCAN Hard Disk Archive Utility Documentation . . . . . .37 Appendix C: KATASK Batch Menu Facilitator Program . . . . . . . . . . .38 Appendix D: Provided DBS-KAT Files. . . . . . . . . . . . . . . . . . .39 Appendix E: Minimum Computer Files Needed To Operate DBS-KAT. . . . . .40 Appendix F: Why DOS 2.X Users Should Update To DOS 3.2 or DOS 3.3 . . .41 DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 3 ABOUT THIS MANUAL ----------------- GENERAL A section is designated by a centered & underlined heading. Centered but NOT underlined headings are referred to as a subsection. Absolutely, do not use DBS-KAT prior to thoroughly following the installation instructions, including restarting your computer after fol- lowing the installation instructions. This manual explains what you minimally need to read in order to use the software. After you are comfortable with the program, or if you have additional questions, you can print out & read the TECHNICAL REFERENCE MANUAL. Please read each section of this manual before using DBS-KAT. It won't take you long. TRADEMARKS: "COMPAQ & COMPAQ PLUS" are trademarks of COMPAQ Corporation. "MS-DOS" is a trademark of Microsoft Corporation. "PC-DOS & IBM" are trademarks of International Business Machines Corp. "PC-WRITE & Quicksoft" are trademarks of Quicksoft. "DB-VISTA" is a trademark of RAIMA Corporation. "Lattice" is a trademark of Lattice Inc. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 4 INTRODUCTION ------------ OVERVIEW DBS-KAT is an easy, practical, super capacity diskette cataloger for owners of IBM PC computers & compatibles. Without sacrificing processing performance, it can manage up to 9,999 diskettes & 16 million filenames in one central database. Three support & companion programs to DBS-KAT are included on the DBS-KAT base system diskette: KATSCAN, KPRINT & KATASK. KATSCAN is a stand-alone program for managing & locating files on a user's hard disk. KPRINT is a print program for programmers. KATASK is not documented outside of this manual, but is a program that enables a user to respond to a menu display inside a DOS batch command file. All of these programs are used by DBS- KAT & need to be installed along with the other DBS-KAT software. Although this manual explains how to print out the documentation for KATSCAN & KPRINT, they are not discussed in this manual. Appendix C documents the KATASK program. DBS-KAT is primarily aimed at hard disk owners, who utilize floppy dis- kettes or removeable disk cartridges. However, if the hard disk owner has a tape device, such as made by ADIC (Advanced Digital Information Corp., Redmond, WA), which fools DOS into thinking it is a large diskette, then DBS-KAT should be able to process the filenames on those tape cartridges. If you are able to do so on a non-ADIC made tape drive, please report your success to Applied Foresight. There are other diskette catalogers, all of which seem to be addressed to floppy disk owners, for only one of them can contain more than a few thousand file names, & that one only 32,000 file names (however, it costs $69). These other products, in the reviewed version levels, respectively can only handle a maximum of 780, 3000 & 4,326 filenames in one diskette catalog file. DBS-KAT is 99% written in the C programming language (Lattice C), the remainder in Assembler. It uses a run-time royalty-free & license-free network model database manager, called DB-VISTA by RAIMA Corporation, 11717 Rainier Avenue South, Seattle, WA 98178. Another benefit of DBS-KAT is the printer program which printed this manual for you. KPRINT has an abundant number of printer features which makes it ideal for printing out source code of programs & other types of plain ASCII files. It has gone through over 35 upgrades because of numerous upgrade requests. Online help is available by just typing in KPRINT & pressing the ENTER key. PHILSOPHY OF DBS-KAT DBS-KAT follows the DB-SHAREWARE distribution concept, developed by DBS- KAT's author & separately explained in THE DB-SHAREWARE PROGRAM manual. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 5 The purpose of the DBS-KAT software is to maintain a master catalog of all diskette filenames that can be inquired against quickly to inform you which diskette(s) contains the filename(s) you are looking for. Simply put, DBS-KAT requires that you physically label all your diskettes starting with the label 0001 up through 9999 & that you stack your dis- kettes sequentially in numeric order. Although, you are recommended to software label these diskettes (DBS-KAT lets you do this while within the program; DOS lets you do this with the FORMAT /V or LABEL programs), DBS- KAT does not require it & supports cataloging diskettes with or without existing volume labels. It makes no difference how unrelated any neigh- boring sequenced diskette is, for DBS-KAT will provide the logical orga- nization to your diskettes. Then all you have to do is let DBS-KAT "look" at each one of your diskettes as they are used. Simply doing this, DBS-KAT can always tell you quickly where is something you want. You can start using your diskettes to contain critically needed current files. You can delay updating the hard disk capacity of your com- puter. You can start thinking of your diskettes as being as accessible to you as another hard disk subdirectory, for you will be able to find out directory information about any file you have worked with, regardless of whether it is currently on your hard disk or now on a floppy. The philosophy of DBS-KAT is to make managing your diskette filenames as effortless as possible. Once you have installed DBS-KAT, & set up your system control record, the minimal amount of typing you have to do in the lifetime of a single diskette, while you are inside the DBS-KAT program, is to assign a 4 digit ID number, once, to the diskette. Everything else is automatically done for you based upon the directory information con- tained on the diskette & the default information for diskettes existing in the system control record. Alternatively, if you so desire, you can maintain unique information about individual diskette volumes. When you run the DBS-KAT program, you indicate whether you want to be prompted for manual entry of volume label textual information or whether you desire to avoid these prompts & to instead have default information apply. USING DBS-KAT WITH THE IBM AT The subdirectory which a diskette file may optionally reside in is cataloged by DBS-KAT without requiring any action by the user. Many IBM AT owners may appreciate this feature. With the 1.2 MB capacity floppies, there is increasing use of making subdirectories on floppies. You do not need an IBM AT to make subdirectories on your floppies. Just type: MD A:\SUBDIR & press ENTER to create the directory called, \SUBDIR, on drive A. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 6 DBS-KAT BASE SYSTEM FEATURES The KATBOOK print procedure printed a two page (80 column printout) equi- valent of the DBS-KAT overview page. Everything described on the overview page is on this diskette. This is NOT demo software! DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 7 HARDWARE REQUIREMENTS --------------------- MINIMUM REQUIREMENTS You minimally need the following for DBS-KAT: 256K RAM memory free (320 KB RAM available); Fixed Hard Disk -- see exception note below; 80-column monitor; MS-DOS or PC-DOS 3.0 or higher (see Appendix F is you have DOS 2.X); a CONFIG.SYS file [create or modify yours as instructed in this manual]; IBM PC,XT,AT,PS/2 or compatible You are advised to have at least 262,144 bytes of RAM or 256K RAM free before running DBS-KAT. Therefore, you should have at least 320K RAM available. DBS-KAT may run slightly under that amount of RAM free space, but you do so at your own risk. RECOMMENDED OPTIONS The following options are recommended. a computer printer capable of continuous printing & printing 80 columns per line; a RAM disk-emulator (requires additional memory & RAM software) to hold frequently called subprograms & run-time, temporary work files; The printer will allow you to use those options which utilize the printer. The RAM disk-emulator will not give you any extra features, but will provide better performance. If you are a novice DOS 3.00+ user, you don't need to immediately worry about what a "RAM disk" is & how to create one. Over the weeks or months that you use DBS-KAT, you might want to buy a DOS tutorial book, which will educate you about DOS & what a "RAM DISK" is. But for now, ignore discussions about "RAM DISKS". PC-DOS 3.0 supplies the capability to create a RAM disk. If you consider yourself past the DOS novice stage, read up on your CONFIG.SYS & VDISK.SYS files. COMMENTARY In lieu of a fixed hard disk, if you own an IBM AT with dual floppy drives, one of them being a high capacity 1.2 MB disk drive, you could conceivably use this software. With the DBS-KAT software, cataloging 200 diskettes & 5,000 filenames will require less than 654 KB of space. This 654 KB figure includes the DBS-KAT software space requirements. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 8 You may ask: "How will DBS-KAT help me avoid needing extra hard disk space if DBS-KAT will swallow so much disk space?" The answer is that if you could rapidly access data files from your diskettes as easy as you currently do a DOS DIR command for the location of a desired file & your subsequent change to another hard disk directory to access that file (else your COPY command against that file residing in the other directory), then chances are that you would find yourself with 20-40% more free space on your hard disk. DBS-KAT allows you to offload between 20-40% of your hard disk space, which is probably now eaten up by moderately or infrequently accessed data files, on to floppies. You can leave your hard disk to keep executeable programs & required companion files (e.g., program Help or Screen files), as well as constantly accessed data files or databases. You are advised to always offload files twice to different diskettes before deleting these files on your hard disk. There are other reasons for DBS-KAT, which offset the disk space that DBS-KAT imposes. These other reasons are rapid access to archived files & prior version files. If you acquire the add-on software modules, you'll have additional reasons to put up with the slight loss of hard disk space because of DBS-KAT. Type KAT -O for a printout about the add-on software modules. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 9 INSTALLATION ------------ OVERVIEW Installation requires that you configure your operating system environment to satisfactorily accomodate database management processing & that you install the software on your hard disk. For those users who understand DOS well & are impatient to proceed on to the next section, I'll state the installation procedure fast. If you don't know what is being talked about, skip the following subsection & print out & refer to the accompanying manual, INSTALLATION FOR NEW COM- PUTER USERS. In that manual, you'll be walked through the installation procedure step-by-step, slowly. At the end of either installation method, you'll end up with some install files that don't need to be on your hard disk. Appendix E lists the files which the install process has you put on your drive. To delete the unneeded files from your hard disk, position your cursor in the same directory on your hard disk where you installed DBS-KAT & type: DEL KATAD.* DEL USQ.* DEL KATBOOK*.* DEL *.EQE DEL *.FQM DEL READ.ME If you have problems installing, or with DBS-KAT, refer to the section in this manual, "Trouble Shooting Tips." SHORT INSTALLATION INSTRUCTIONS FOR THE DOS 3.0+ EXPERIENCED USER Installation requires the following specific acts (assume drive A is a floppy & drive C is a hard disk): 1. Make a duplicate copy of your DBS-KAT diskette for archival pur- poses. 2. Put the DBS-KAT diskette in drive A. Type: C: MD \DBSKAT COPY A:KATDB.* C:\DBSKAT/V You are highly recommended to put your KATDB.* files in the sub- directory, \DBSKAT. If you put them in any other subdirectory, then you must always invoke a DBS-KAT program with a -L option & be sitting in that directory at run time. Specific syntax examples are given later. (If you install the KATDB.* files in the root DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 10 directory, DBS-KAT will detect that without you having to first move their as well.) Putting the KATDB.* files in \DBSKAT, means that you can be any- where on your hard disk & from that location run DBS-KAT. However, if you install the DBSKAT programs there, this assumes that you have a PATH statement which minimally encompasses the \DBSKAT directory. The following PATH statement might be a typical path statement to use: PATH=C:\;C:\DOS;C:\UTIL;C:\DBSKAT If you need to create or update your PATH statement, include the PATH command line (such as the above) in your C:\AUTOEXEC.BAT file. If you don't have a C:\AUTOEXEC.BAT file, then minimally create one which looks like the one below. Use any editor which can update a plain vanilla ASCII file (e.g., EDLIN, PC-WRITE, EC). The PROMPT line is optional. It will show you to the left of the prompt sign, your current directory area. A minimal C:\AUTOEXEC.BAT file should include: DATE TIME PATH=C:\;C:\DOS;C:\UTIL;C:\DBSKAT PROMPT ($P) If you are DOS 1.1 experienced, the filename "C:\MYFILE", means a file, of the name "MYFILE" which resides in the root directory "\" of drive "C:". If your cursor is positioned already in the root directory of C:, then you can ignore the "\" symbol. 3. Put the remaining DBS-KAT diskette files somewhere along your PATH (or \DBSKAT if you've updated your PATH statement). Include in your path, your DOS programs, BACKUP, RESTORE, SORT, MORE & FORMAT. (I suggest these programs and your path support them in a directory called \DOS.) If you don't have or want a PATH statement in your environment, put all the DBS-KAT files except KATDB.* in your root directory and the KATDB.* files in \DBSKAT. For instance, to put everything in your root directory, change your current drive to your hard disk & issue the following com- mands: CD \ COPY A:*.* C:\/V A: KATBOOK (choose the option to decompress & install the DBS-KAT programs in the current hard disk directory) 4. Either create, update, or verify that your C:\CONFIG.SYS file exists & has the following two lines in it: FILES=20 BUFFERS=15 If you have an IBM AT, you could make the BUFFERS=25 instead. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 11 The BUFFERS line is not needed by DBS-KAT, but since you're changing CONFIG.SYS, you might as well optimize your BUFFERS line. 5. This is an optional step & not required. If you don't have a RAM disk, proceed to step 6. If you have a RAM disk, which is uploaded with files at power up time with file copying going on in your C:\AUTOEXEC.BAT file, con- sider putting the following files in your RAM disk. This is not required, but will give you performance improvement. The files include SORT.EXE, which comes on your DOS diskette. The files that you should consider putting in your RAM disk are: SORT.EXE KATSCAN.EXE Consider leaving spare space on your RAM disk of at least 30,000 bytes. This empty space can be used by DBS-KAT for its run-time, temporary work files. The names of these run-time files are KATWORK1.DIR & KATWORK2.DIR. You may have to update your C:\CONFIG.SYS if your RAM disk space alottment is done in that file. If you use IBM AT high capacity floppies & store a high number of files on them, you may need to allocate more than 30,000 bytes to accomodate these work files. Put the drive designation for your RAM disk at the start of the left hand side of your PATH statement, so that your RAM disk gets looked at first down your PATH. If drive D is your RAM disk, then minimally your PATH statement should include: PATH=D:\;C:\;C:\DOS;C:\UTIL;C:\DBSKAT To avoid DOS executing these two programs from your hard disk, make sure that SORT.EXE & KATSCAN.EXE will not exist in any PATH directory other than D:\, nor let them exist in the current directory where you have your DBS-KAT database. Consider creating a directory called \OFFPATH & moving these two files there. In your \AUTOEXEC.BAT file copy the \OFFPATH directory to your RAM disk. 6. If you updated CONFIG.SYS or AUTOEXEC.BAT, restart your computer now. DO NOT SKIP THIS STEP! 7. Excepting those with less than 100% IBM PC Compatibility (including those who use a Hercules monochrome/graphics card) or those who power on their computer with a startup diskette, you can go to the next section, "Updating The DBS-KAT System Control Record." Those whose computers are neither IBM nor as compatible to an IBM as a COMPAQ is, should read the next subsection before proceeding to the next section. Those who use a startup diskette should read the section immediately following. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 12 INSTALLATION FOR NON-IBM COMPATIBLE MS-DOS PC OR ANY BRAND PC WITH A HERCULES CARD The author has not tested this software on non-IBM compatible MS-DOS com- puters. It was developed on a COMPAQ PLUS computer however. The rapid display of DBS-KAT's signon & usage screen is the most IBM specific piece of code knowingly used. As said, this does work on a COMPAQ PLUS. However, it might not work on less compatible MS-DOS computers. For sure, the default fast screen method does not work with a Hercules Monochrome/Graphics Card. For this reason, the user can disable this direct IBM-type screen use. To do this, type in the following, with your prompt at the "C" level. Type: ECHO X>\IAMNOTAN.IBM & press the ENTER key. This is all you have to do. What you've done is create a one byte file in your root directory of your hard disk. The drive must be the same as the drive where your database resides. DBS-KAT will utilize a less machine specific screen display method if it finds this file to exist. ADDITIONAL INSTALL INFORMATION FOR HARD DISK USERS WHO POWER ON THEIR COMPUTER WITH A STARTUP DISKETTE 1. These instructions will assume that drive A is your floppy & that drive C is your hard disk. Also assumed is that during your following the installation instructions, that you inspected, & if needed, updated the CONFIG.SYS & AUTOEXEC.BAT on a bootup floppy diskette. Insert your bootup floppy in drive A. Make sure you don't have a write-protect tape on your floppy. If so, temporarily remove it. 2. Type: COPY A:COMMAND.COM C:\/V & press ENTER. If you ever update your operating system, be sure to repeat this operation with the new COMMAND.COM. 3. You must add a "SET COMSPEC" line to your AUTOEXEC.BAT file first so that DBS-KAT will think you powered on off your hard disk. Do the below: 3.A. At the "C" prompt, type: EDLIN A:AUTOEXEC.BAT 3.B. At the "*" EDLIN prompt, type: I 3.C. Type: SET COMSPEC=C:\COMMAND.COM 3.D. Press the F6 function key & press ENTER. 3.E. Type: E 4. Restart your computer now, using your updated bootup floppy disk. If you have a backup of your bootup floppy disk, make sure the backup gets the new AUTOEXEC.BAT put on it. You must do this restart of your computer in order for DBS-KAT to work correctly. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 13 UPDATING THE DBS-KAT SYSTEM CONTROL RECORD ------------------------------------------ Before you can regularly use DBS-KAT to process & inquire against dis- kettes, you must first update DBS-KAT's System Control Record, which keeps track of your database as well as holding your default value entries. This manual explains the program prompts. You can then actually update your system control record, taking mostly the default values, except where it is obvious that you should over-ride the provided default. If you update your system control record after reading this section, come back to this manual & read the remaining sections before using the rest of DBS-KAT's features. You minimally only need to update your system control record during DBS- KAT's install process. The program used to update the system control record is a subprogram within the inquiry program, KATLOOK.EXE. To perform this, you should be somewhere on your "C" drive with your prompt ready to receive a command. Either type: KATLOOK -M & press ENTER or type: KAT -M & press ENTER. Don't forget the minus sign (hereafter called the "dash") if you type: KAT -M. Typing KATLOOK -M will actually load the program faster, as the other method first loads the KAT program which in turns loads KATLOOK with the "-M" option. If you installed DBS-KAT in a subdirectory, type either KATLOOK -ML or KAT -ML. After receiving a logo display, you'll get the message "No System Control Record, --Putting you into add mode." You'll be prompted for a variety of fields, in each case you'll be shown the allowed maximum width of your answer. In some cases, you'll be shown a default answer you'll get if you just press ENTER. The prompts that you will be shown are reproduced below. Supporting comments are provided, when needed, alongside. Alternatively, if you have previously added a System Control Record, you'll be put in the update mode where the prompts are so similar, that they do not needed to be documented here. However, you are not allowed by this program to update the database owner's name, once you insert it into your database. This is because of the security arrangement of DB- SHAREWARE, -see the manual on DB-SHAREWARE for more information. When DBS-KAT is done processing the system control record, your database is closed & you are exited back to the DOS prompt. For the current software release of DBS-KAT, you are unable to change the database owner's password, which is the password needed to change the user's password. The reason for this is unrelated to security reasons, & if enough users request it, the ability to change this password will be allowed in a future release. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 14 However, if you misspell your name or the database owner's password, you are allowed at the end of the system control add function to start the add process over again. Once you've added the system control record, then unless you want to start again with a totally empty database, you will be unable to change these two fields again using this program. You can update the database owner's name, by ordering an add-on software module, because on the order form (type: KAT -O), you specify the new (or same) database owner's name which the add-on software program will use to update your old database. All prompts require a response except where specified as "optional." When you are given a default response (shown above the allocated space for your answer), you can take the default response by just pressing the ENTER key. Many of these prompts will be repeated during each diskette you process, unless you chose at run time to have DBS-KAT skip prompting you & to instead use the default answers set up in the system control record. These prompts which are capable of being repeated for each diskette being processed have the parenthetical statement "(for diskette vol. info.)" shown beneath the prompt. At run time, the actual wording of the prompts may in some cases be up to 10 percent longer. For space reasons, they are shortened here to allow more space for the right hand commentary. PROMPT ----------------- COMMENT--------------------------------------- Database Owner's Name You are required to enter your name or that of your company. This name will be shown to you each time that you run DBS-KAT in the manner described in the DB-SHAREWARE manual. This field is the only field which will preserve lower case input. All other fields in DBS-KAT will upper case your input as it is stored in the database. Database User Password The only place that DBS-KAT can optionally (optional) have a security concern is in the inquiry function & password maintenance function. Anyone can always update your database (except the password portion). The thinking behind this decision is that you might have your secretary or assistant update your database as they update your diskettes. However, if you have hundreds of diskettes, you might have some of them devoted to con- fidential topics, which might be revealed in their file name or volume (DBS-KAT entered) heading. You might want the location of these diskettes hidden. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 15 Thus you can ask that DBS-KAT checks for a user password (which you set up) of anyone asking to inquire against the database. Password to chg password Since you may allow more than yourself the (optional) right to inquire into your database & you may later change your mind about another person's right to look into your data base, a password beside the user password was needed. Consider this the owner's or administrator's password. IMPORTANT! Do not ever forget this password! If you forget it, there is no way you can use either the existing DBS-KAT software or DEBUG's dump command to uncover this password. A proprietary encryption method stores this password in your database. Use a password that is impossible for you to forget, yet which is one others won't ever guess, such as a childhood nickname no longer used, or your first date's name, etc. You may want to write your password down & store it in your safe or safety deposit box. Note: if you decide not to implement this administrator's password during the initial add system control process, you are never given the opportunity to change your mind. If you aren't excited about requiring a password at inquiry time, you might want to implement an administrator password, but skip for the time being a user password. If you know the administrator password, you can always assign a new user password via the update system control process. Default loc: H(ome)/W(ork) The default location is W(ork). You can change the default location to H(ome). See next prompt for more information. Enter begin no. for home The default number is 0001. DBS-KAT allows designating the location of your diskettes to be either at work or at home. Some of the DBS- KAT users may be using a COMPAQ PLUS & thereby be tracking diskettes at both locations. The purpose of this field is to save you key- strokes in assigning the volume ID for your diskette. You are always allowed to over-ride the prompted default value. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 16 Enter begin no. for work The default number is 5001. # of disk upds b4 sugg.bu Because DBS-KAT involves a database, you are suggested to periodically back up your database, in case unpredicatible interrup- tions, whether hardware or otherwise caused, destroy your database. At the start of each diskette to be processed, you are given the option to backup the database. However, you may decide to methodically back up the database every so many diskettes. If you desire a periodic reminder, insert the desired interval here, otherwise assign a very high number (e.g., 99). Enter diskette drive char Typically, you'll probably choose the default letter, A. However, you can choose any legit- imate floppy disk drive, or drive which acts to DOS like a floppy disk drive (refer to earlier comments in the Hardware Requirements Section). If you have an IBM AT, & alternate between drive A & B, you should pick the letter used the most often. You are given the opportunity inside the cataloging program to over-ride this letter. Enter KATWORK1.DIR drive DBS-KAT during its processing of a diskette, ENTER KATWORK2.DIR drive will run another program, KATSCAN.EXE, which creates a directory display file of your entire diskette, even if it has subdirectory- located files on it. The unsorted directory display file is called KATWORK1.DIR. DBS-KAT then runs your DOS program, SORT.EXE, against this KATWORK1.DIR file & outputs the sorted version of this file under the name KATWORK2.DIR. If you have an electronic RAM DISK, indicate its drive letter here. The default drive letter is the typical hard drive letter, C. If you will alternate cataloging diskettes & removeable disk cartridges, setup the system control record with the parameters you want for the diskette drive. Using the "S" option in the catalog update process (KAT -U), you can switch to cataloging your removeable disk cartridges & the program will let you change for the session (or until you choose the "S" option again, whichever comes first) the para- DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 17 meter settings for the: (a) target drive being cataloged, (b) drive to use for work files, (c) & sector size of device being cataloged. Default From Hd Drive Typically this is drive C, the default. If (for diskette vol. info.) you ask DBS-KAT to prompt you for each dis- kette being processed, you'll be prompted for the source hard disk drive, & be given this letter as the default answer. Default vol. pathname The default hard disk source pathname for your (for diskette vol. info.) diskette file is "VARIES". If you catalog a diskette with no files on it, & you've asked not to be prompted for volume heading information, DBS-KAT substitutes a blank pathname. The idea behind the pathname is to have the inquiry function act similar to how you inter- rogate your directory on your hard disk. On your hard disk, you'll typically move yourself to a directory, & then query a file set against only that directory. For example, if you are in a directory for your word processing files, the DIR *.DOC will scope word processing files, whereas if you have a directory for your programming devel- opment, the DIR *.DOC might scope program development or usage documentation files. However, to minimize database overhead both to reduce disk space utilization & update pro- cessing time, the directory database is not structurally segmented by pathname. Doing an inquiry similar to a DIR *.DOC against your \WORK directory, will involve scanning your database from the very first record through the very last record. Thus, you'll probably want to minimize inquiries where the leading characters of the filename are irrelevant. Default vol. note This is a 13 character field, which can be (for diskette vol. info.) thought of being a commentary field on the diskette's contents or a place for extended path information, in case your source hard disk pathname is longer than 8 characters long (e.g., \LOTUS\TEMPLATE\DOC). Examples of appropriate comments might be "NORTON UTILS", "XTALK" or "LOTUS". The default note for your diskette volume heading is "MISC". If you catalog a diskette DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 18 with no files on it, & you've asked not to be prompted for volume heading information, DBS- KAT substitutes "SCRATCH" for the volume heading note. Default YY+Qtr buy disk You might want to keep track of how old a (for diskette vol. info.) diskette is. The default answer, zero, will substitute the current YEAR & QUARTER (con- catenated together as a 3 digit number). When first entering in all your old diskettes, if they are on the average 9 months ago, you might want to indicate the YY+Qtr for that period. Then after your initial database load, you could change the default value back to zero. Diskette Format OP SYS Indicate here the default for whether the (for diskette vol. info.) diskette is normally formatted under IBM PC DOS ('P'), which is the default, or under MS DOS ('M'). These letters do not cause anything special to happen, except that they will be redisplayed on some screen outputs. You can use alternative letters if you wish. OP SYS Ver. (no dec.pt.) Indicate here the default for which DOS (for diskette vol. info.) version number, the diskette was formatted under, however do not use a decimal point (wasted storage & display space to carry the decimal). Thus 200, the default, refers to 2.00 DOS. Usual seq_typ is You may be processing a group of related (for diskette vol. info.) diskettes. The grouping may be because you are using the DOS BACKUP command (type 'B'), which is the default or because you are cataloging a software package containing more than one dis- kette (type 'P'). You are free to invent other sequence types. However, use 'B' for the DOS BACKUP sequence type. Future software may act upon this information. For now, just indicate, that when you are pro- cessing a sequence of diskettes, what will be the normal sequence type. Don't worry if most of the time you will not be processing a sequence of diskettes. Disk usually part of set Indicate 'Y' or 'N' (the default), whether the normal diskette you intend to catalog will DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 19 belong to a sequentially related set of dis- kettes, such as a full backup set, etc. Enter DOS cmd for B/U You are highly recommended to perform your PC KAT database backup under DBS-KAT supervision. The default method is via the DOS BACKUP command ("BACKUP C:\KATDB.* A:"). You can insert any valid DOS command here to accomplish your backup. Your DOS command could even be the .BAT file name to do your backup (leave out the ".BAT"). The database will be updated that you are about to do a backup, then the database will be closed prior to your backup. Also, your DBS-KAT log file will note the occurrence of a backup being performed. More about this log file later in the manual. Enter label utility name DBS-KAT comes with the free, user group program, VOLSER Version 2.00, Copyright 1983 by T. A. Davis. As T. Davis does not provide an address either in his program or his docu- mentation, Applied Foresight is unable to ask his permission or to ask users of DBS-KAT to voluntarily contribute an appreciation token to Mr. T. A. Davis. VOLSER is a label utility. With VOLSER or an alternative software label utility, which you would select here, you can update your diskette with the volume ID four digit number (use leading zeros to make the volume ID 4 digits). Having the volume ID software embedded onto the diskette, saves DBS-KAT from having to ask you each time what is the number on the sticky label outside your diskette. Oh yes, you should have a four digit volume ID on a sticky label outside your dis- kette. If you don't care to use VOLSER, indicate the label utility program of your choice. Norton's Utilities comes with the program, LABEL. IBM PC DOS 3.0 comes with its utility program, LABEL. Make your choice known to DBS-KAT. The unaltered documentation on VOLSER by T. A. Davis, is in the file, VOLSER.DOC, which is on your PC KAT diskette. Entries Okay The default answer is 'Y' for Yes. If you want to change one of your answers made above, you DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 20 should answer 'N' for No. You'll be reprompted for every field again, starting from the first prompt. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 21 CATALOGING DISKETTES -------------------- INVOKING DBS-KAT Efficient & rewarding use of DBS-KAT involves continually keeping your database up to date about the contents of all of your diskettes. This is done by the diskette cataloger program function, which can be invoked in a variety of ways. You can enter the commands in upper or lower case, it makes no difference. These commands are entered at the DOS prompt level. INVOKE CMD COMMENT------------------------------------------------- KAT -U Catalog diskettes until requested to exit or backup my database. Provide prompts, with defaults shown, to add or update unique diskette volume information. KAT Same as above, except first show program options help page. Check if program has been installed & the System Controlled record has been updated. Exit with message if not installed yet. When user responds to "Press any key", process as if user had typed "KAT -U". KAT -UH Same as above, except prespecified location is Home. If location is not specified, use default location given in the System Control Record setup. KAT -UW Same as above, except prespecified location is Work. KAT -U2 Same as KAT -U, except only process for two diskettes. KAT -U2H Same as KAT -UH, except only process for two diskettes. KAT -UN Same as KAT -U, except bypass prompting for unique diskette volume information. Use the default values based upon the system control record. For those users who habitually name their files in such a manner that just remembering the spelling of part or all of the file name is all that is necessary to know about, those users might be satisfied running DBS-KAT this way. It saves about 30-60 seconds per processed diskette, to use the -N option. Alternatively, on many of your diskettes, you might want to not use the -N option. For instance, you might want to state that the involved diskette belongs to the path, UTIL, & in the note field, state "PC-TALK III", & so forth. However, some users, lazy like the Author, might not care about volume heading information, & rely upon the fact that on this diskette, retrieving by the file name, "PC-TALK", will always enable DBS-KAT to tell me which diskette volume to look for PC-TALK III. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 22 On diskettes which habitually get reused for totally dif- ferent file storage purposes, you might want to always use the -N option. While inside DBS-KAT, you can toggle having this "N" option on or off. KAT -UNH Same as KAT -UN except prespecified Home as the location. KAT -U2NH Same as KAT -UNH, except only process for two diskettes. KAT -UA Same as KAT -U, except floppy to process is on drive A:, regardless of what drive letter the system control record points to. KAT -UB Same as KAT -U, except floppy to process is on drive B:, regardless of what drive letter the system control record points to. KAT -LU Same as KAT -U, except use the database in the current directory. Without the -L option, DBS-KAT will move to the root (\) directory to process a database there. If a database isn't there, but one is in the current directory, it will remain in the current directory. The user can invoke DBS-KAT using valid combinations of the above. Of course, -A & -B can never be used together. Nor can -H & -W ever be used together. The order in which the options are stated are irrelevant, except that only a number can follow the -U option, immediately to the right of the "U". Thus, typing KAT -UN & KAT -NU will perform the same thing. Some of the above options can be chosen from a menu which drives the program. This menu is shown in the "CATALOGING PROCEDURE" subsection below. DISKETTE HANDLING WITH DBS-KAT You should physically & software label all your diskettes with a four digit number. Write-protected diskettes need not be software labeled. A physically labeled diskette means that with a soft felt tip pen, you have written a four digit number which is visible on the diskette gum label which sticks on the outside of the diskette. A software labeled diskette means that when you do a DOS DIR A: against the diskette, that you are shown something like the below as the first two lines of the display: Volume in drive A is 0175 Directory of A:\ DBS-KAT provides you with means to do software labeling from inside the cataloging program. Refer back to the last prompt in the System Control Record. The recommended route is to use the numbers 0001-5000 for dis- DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 23 kettes initially cataloged at Home, & to use the numbers 5001-9999 for diskettes initially cataloged at Work. If you only have one location, then use the numbers 0001-9999. These are only recommendations. Blank volume ID labels or non-4-digit volume ID labels should be minimized to write-protected diskettes, because each time you catalog the diskette, you have to remind DBS-KAT of the volume label number. Diskettes which are 4-digit software labeled, are automatically recognized by DBS-KAT as to what volume label ID it contains. In your diskette containers, you should stack all your diskettes sequen- tially in numeric order. It makes no difference how unrelated any neigh- boring sequenced diskette is, for DBS-KAT will provide the logical orga- nization to your diskettes. However, you'll still find it convenient to keep sequentially logically related diskettes in sequential numeric order, such as for full hard disk backups, etc. The author reserves three neighboring numbered diskettes for his database backups, since with its some 13,400 plus filenames, it goes a little into the third diskette to back up a database this big. Doing this is a convenience not a necessity, for the diskette volume inquiry process will remind you of what follows or precedes a diskette (assuming you told DBS-KAT about the sequencing originally). A "scratch" diskette is one which is either empty of files, or one which has junk or obsolete files on them & can be erased without worry. When DBS-KAT processes a scratch diskette, it labels the database volume header with the word "SCRATCH." You can ask DBS-KAT for a screen or printout of your SCRATCH volumes. However, if you don't want to have to run this inquiry to find out where your scratch diskettes are, you could consider temporarily locating your scratch diskettes in a scratch dis- kette container or separate location. THE CATALOGING PROCEDURE The cataloging program is menu driven & your choices for action are dis- played as follows: ------------------------------------------------------------------------- OPT: DESCRIPTION OPT: DESCRIPTION P Insert diskette now to PROCESS E EXIT program now H change location to HOME W change location to WORK V change database VOLUME header L change diskette volume LABEL D diskette dir/w & DEL option F FORMAT a diskette T TOGGLE vol hdr prompting on/off S SWITCH to another diskette drive B BACKUP database & exit program PARMS ON: Locn=> HOME; Prompting=> ON; Directory=> ROOT; Floppy=> A: P Do: B,D,E,F,H,L,P,S,T,V,W ? > < ------------------------------------------------------------------------- DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 24 Most of the prompts & activity occurring in the cataloging procedure is self evident, based upon the user understanding the system control record update process & being able to read the cataloging procedure displays & prompts. This documentation will cover the portions of this procedure which may not be completely self-evident. 1. In the overview section, DBS-KAT was discussed being smart enough to know that you hadn't made any changes since your last cataloging process against that diskette. There is one ramification to this smartness. If your only change to a previously processed diskette, is that you renamed a file, then DBS-KAT will not process the diskette, because renaming an existing file on a diskette will not impact either of the two captured totals. These two totals, you will recall, deal with the total number of files on the diskette, & the sum total of file dates + times + sizes covering that diskette. 2. When you are displayed the volume heading information for a pre- viously cataloged diskette, you are given the following column headings: VOL# --PATH-- NOTE/EXT-PATH LAST UPDATE #FIL KBLF L F O VER BUY NV TSQ NEXT LAST The unobvious column headings above mean the following: KBLF The number of kilobytes available for additional file use. L Location where the prior cataloging processing took place. F The letter of the hard disk from which these files came from. O The operating system type under which the cataloged diskette was formatted. VER The operating system version number under which the cataloged diskette was formatted. NV The newest version file of all files on this diskette. This information is only available if the add-on software module, which does the aging analysis, is owned & ran against your database. This add-on software module is not yet available, as of the release time of this document. It will be available in a matter of months. When this field is operational, if it contained the number "2" or higher, it would mean that nothing on this file is most recent compared to same named files on other diskettes. You could conceivably reuse this diskette if you aren't interested in prior versions of your files. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 25 TSQ This represents two columns of information without a separating blank space between them: T Sequence type (eg, B=BACKUP, P=SOFTWARE PACKAGE) SQ Sequence number (ie, 01-99). 3. You can remove the diskette from the disk drive which is being cataloged when you see on your screen either of the following two messages. If you have another diskette to process, you can insert it at this time. a) "Will display each input directory filename as it is processed:" b) "Input directory has no files on it--processing as a scratch volume." DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 26 INQUIRING AGAINST THE DBS-KAT CATALOG ------------------------------------- INVOKING DBS-KAT Before you actually update & inquire against your database, you should read the last remaining section, which comes in the next section "MAINTAINING & RECOVERING YOUR DATABASE." The main purpose for having DBS-KAT is to ask it which diskette(s) has such & such file on it? This is done by the catalog inquiry program function, which can be invoked in a variety of ways. You can enter the commands in upper or lower case, it makes no difference. These commands are entered at the DOS prompt level. INVOKE CMD COMMENT------------------------------------------------- KATLOOK This is the quickest way to look at your database. If you chose the alternate route of KAT -D, it would invoke KATLOOK anyway. So you save having to have the computer first load KAT.EXE followed by then loading KATLOOK.EXE if you just type KATLOOK & press ENTER. KAT -D Same as KATLOOK, except computer takes a couple of seconds longer to function. KATLOOK -P Same as KATLOOK, except you request that DBS-KAT does not show in the PATH & EXT PATH/NOTE columns the subdirectory information if the file entry sat in a subdirectory on the diskette. The only thing that would be shown in these two columns would be information from the diskette volume header record. Since most users will not be utilizing subdirectories on their diskettes, KATLOOK gives the same results as entering KATLOOK -P. KATLOOK -P was inserted into the product during the debugging phase of catching the individual file entry elongated directory name at display time. You'll recall from the Overview subsection in the Introduction that the database only carries a numeric code for the subdirectory diskette location it belongs with in each database record. However, this feature was left in the program, since some users might want to take advantage of this option, & it really causes no overhead to the program's performance to leave it in. KAT -DP See above discussion about KAT -D. Otherwise, this is the same as entering KATLOOK -P. KATLOOK -L Inquire against the database located in the current directory. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 27 KAT -LD See above discussion about KAT -D. Otherwise, this is the same as entering KATLOOK -L. THE INQUIRY PROCEDURE The inquiry program is menu driven & your choices for action are dis- played as follows: ------------------------------------------------------------------------- CHOOSE TYPE OF DIRECTORY DISPLAY DESIRED: 1. Process individual dir argument line. 2. Process all cataloged files for a given volume number. 3. Process all cataloged files for the entire database. 4. Listing of cataloged diskette volumes. 5. Listing of uncataloged diskette volumes. 6. Exit program. 6 Enter option number: > < ----------------------------------------------------------------------- Most of the prompts & activity occurring in the inquiry procedure are self evident, based upon the user understanding the cataloging process & being able to read the inquiry procedure displays & prompts. This documentation will cover the portions of this procedure which may not be completely self-evident. 1. If your database was set up with a user password, you are asked for it in this program. You must provide the user password in order to inquire against the database. When you type in your password, you will not see what you type in nor will your cursor move. That is normal. This way, your friend behind you won't see your password. 2. When you are displayed the filename heading information, you are given the following column headings: VOL# FILENAME.EXT FLDATE FLTM --SIZE- --PATH-- NOTE/EXT-PATH LTSQGT LAST-UPDATE With the exception of "FILENAME.EXT" & "LTSQGT", the above column headings also appear in the previous section in "THE CATALOGING PRO- CEDURE" subsection. Two exception to being the same as THE CATALOG PROCEDURE heading are the "--PATH-- NOTE/EXT-PATH" headers. These columns will show the actual diskette subdirectory (the first 22 characters) which the cataloged file sits in, if such is the case, rather than the volume heading Note/Ext-Path information. Again, if the diskette file does not reside on the diskette in a subdirectory, the shown information derives from the volume label record. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 28 LTSQGT represents five columns of information without a separating blank space between them. L Location where the prior cataloging processing for this disk took place. T Sequence type (eg, B=BACKUP, P=SOFTWARE PACKAGE). SQ Sequence number (ie, 01-99). G How many generations old is this filename in relationship to the most current file with this same FILENAME.EXT, which is gener- ation 0. Generation 9 would be for the 9th plus higher genera- tions. This information & that of the following adjacent field is not updated by the base package. An add-on software module program, which does the aging analysis, will update this field. T Is the generation number for this FILENAME.EXT tied ("Y" or blank). 3. If you choose the directory display option number 1 (Process indi- vidual dir argument line) & ask to "Suppress console output", you can ask that the displayed output go either to the printer or to a file. If you choose a file output, you are given the opportunity to use the filename, KATDIR.OUT, or you can create your own valid filename. File-directed output will not contain the column headings. A DOS batch command file, KATSORT, is provided which will sort KATDIR.OUT in reverse chronological order. You must exit this program & execute the procedure, KATSORT, at the DOS prompt level. 4. If you choose the directory display option number 1 (Process indi- vidual dir argument line), you might be a little unfamiliar with your search options. The program at this point displays the following instructions: "For your search argument, you'll be asked for a string value & how to use this string in the search (exact compare, anchored sub- string compare, or un-anchored substring compare - E, A, U). You are not allowed to use the following characters: '*', '?', '+'. Just pressing ENTER for a string value indicates no restriction." The DOS DIR command provides an anchored substring search capability. If you typed: DIR AUTO* & pressed ENTER, you would be doing an anchored substring compare. Although DOS does not provide an un- anchored substring search, if it did, typying: DIR *TO* & pressing ENTER, would provide you with a list of filenames where floating any- where in the filename portion are the two neighboring characters "TO". This is an example of an un-anchored substring search. Although, DBS-KAT provides an un-anchored substring compare, this type of search on the filename portion will cause every filename entry in your database to be scanned, which can take awhile depending on the size of your database. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 29 The TECHNICAL REFERENCE MANUAL overviews the structure of DBS-KAT's database design & provides an elaborate example list representing a range of searchs ordered by a most efficient search argument to a least efficient search argument. However, don't be afraid to use the search strategy you need to accomplish the job you want done. With a 12,000 record database, best case searches are a few seconds long & worst case searches are a few minutes long. 5. If you choose to provide a path argument search & to have it used against cataloged filenames, it is used against the diskette volume label pathname, unless the file is residing in a subdirectory on the cataloged diskette. In that case, you can search for the file by providing the name (or part of the name) of the subdirectory; however, instead of using a backslash character, use a foreslash character (/) to indicate the directory slash. DBS-KAT converts the directory slash to a foreslash (/), when updating the database. 6. If you choose to only provide a path/note argument search (no filename/ext search argument), you'll be asked if you want the search to be only against cataloged volume header records rather than against cataloged filenames. Choosing the volume header search will make your scan a whole lot faster. 7. Diskettes that are empty of files are marked "SCRATCH". By providing a path/note argument with the value "SCRATCH" or "scratch" & to have it used only against cataloged volume header records, you will be provided with a list of scratch diskettes. 8. Option 3 now supports unloading the entire database to a flat file or processing the entire database within a beginning and ending date range. Try option 3 and play around with the combinations. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 30 TAKING CARE OF YOUR DATABASE ----------------------------- OVERVIEW This section covers the following activities: 1. Conservative Updating 2. Backup 3. The Log File 4. Integrity Analysis A related section on Recovery is included in the TECHNICAL REFERENCE MANUAL, because not every user will ever need it. However, every user should be prepared for it by following the recommendations below. CONSERVATIVE UPDATING Databases are delicate creatures. Most programs which work with data- bases, assume that all the proper connections are made between the dif- ferent records in a database. Such programs, when they come across the first data record with its associated pointer addresses to another record failing to properly point, will abort. Thus often a very large database is at the mercy of one bad pointer. Pointers, like other portions of a disk file, can be disturbed by a variety of external hardware & software factors, many of which lie totally outside of the software which is spe- cifically written for the database. Conservative practices are to frequently backup up the database & to do a periodic integrity analysis of the database. If you're doing a hundred or more diskettes in the beginning in a day, then maybe every 33-50 dis- kettes, back up your database. If you're updating a few diskettes per day, then one or two days a week you should back up the database. BACKUP You are advised to back up your database while inside the KAT -U (or any variation of the -U option) program. Your database backup will be made according to the instructions you gave DBS-KAT in updating your system control record. Most persons will want to take advantage of the default backup command which one is prompted with during the system control record add process. During the KAT -U program session, you can choose to backup your database at the beginning of each processing loop, or after you have processed the number of diskettes equal to the reminder interval count you provide DBS- KAT in your system control record update process. The existence & usefulness of your log file is discussed shortly, however it relevant to note now that DBS-KAT records in this log file when you DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 31 made a backup of your database. It also makes a record entry, including the volume number, of each updated diskette. For the above reason, it is a good idea to update DBS-KAT against the diskettes you just backed up your database onto, right after doing the backup & before processing any other diskettes. This way, when you inter- rogate your log file, those diskettes which immediately follow a backup record entry are the diskettes which contain your database. This is useful, when looking for your couple-to-several generation old set of database backup diskettes to reuse. You can also use DBS-KAT's inquiry function to find out the same information, but some people may prefer one method over the other method. The log file's main purpose is for recovery & not for locating backup diskette. Despite DBS-KAT's ability to inform you of which diskette follows in a sequence, you'll still find it more convenient, if your database backup span across neighboring numbered diskettes. Thus when you initially number your diskettes, you might want to set aside 3-4 neighboring sequence for backing up your database. It currently takes about 2.5 dis- kettes to backup a database containing 13,400 plus directory entries, which covers about 600 diskettes. You should felt-tip label these dis- kettes, beside the normal 4 digit number, with information such as: 0333 KATDB.* 1 of 4 See 0334-0336 Verified: 850301/850501/850701 850901 The above label shows the following information: 1. The volume ID number for this diskette. 2. Information that the diskette contains a backup of the database. 3. Information that this diskette is number 1 of a set of 4 backup diskettes. 4. The numerous different dates for which this database was a backup of a database right after it had been okayed via a database integrity analysis run. In this instance, the verify dates spill over onto line four of the label. In conjunction with using the DOS BACKUP command, one should periodically perform a CHKDSK /F. In the April 23, 1985, issue of PC WEEK, a letter to the editor by a VP of SyntheSys Consulting Inc., Syracuse, NY, entitled "Fixing BACKUP Bugs," refers to "problems with the [BACKUP] program if CHKDSK detects any errors on the disk you are trying to back up. The user should be sure to use CHKDSK to correct any problems with the hard disk before using BACKUP (i.e., use CHKDSK with the /F option)." THE LOG FILE Each diskette that you process by DBS-KAT causes a record to be written to a plain ASCII-type file (useable by most word processors), called KATDB.LOG. When you backup the database is recorded here too. The DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 32 information written about the diskette processed is in the following format (example data displayed beneath the format). The format heading here does not appear in the file, KATDB.LOG, nor by the KATLOG printout. LN LOC VOL# YYMMDD HHMM TOT-REC-COUNT 1 H 0075 850503 1354 13035 2 H B/U 850503 1355 3 H 0174 850503 1400 13039 4 H 0175 850503 1400 13043 5 H 0176 850503 1401 13047 6 H 0199 850503 1401 13099 The main reason for this log file is in the unlikely event that something happens either to your hard disk or to your database & you need to do a recovery using an earlier backed up database. The exact procedures you'll follow are given in the TECHNICAL REFERENCE MANUAL. Another usage for the log file, if you want to use it in such a manner (as shown in the above example), was earlier discussed in the subsection, BACKUP. The above example reflects the fact that after processing volume 0075, the user backed his database over three diskettes, 0174-0176, after which he updated DBS-KAT with the directory information of diskettes 0174-0199. A DOS batch procedure file, called KATLOG.BAT, is provided to aid you in inquiring against your log file. KATLOG can be invoked in a variety of ways. You can enter the commands in upper or lower case, it makes no dif- ference. These commands are entered at the DOS prompt level. INVOKE CMD COMMENT-------------------------------------------------- KATLOG Typing just this causes the entire log file to be con- tinuously printed, using the KPRINT program. KPRINT is explained in Appendix A. Lines numbers are printed for this option. KATLOG 35 Any number is allowed. Typing this causes the last 35 lines of your log file to be displayed to your screen. KATLOG uses your DOS program, MORE.COM, so be sure to have it available (via your PATH) to be executed in the directory from which you execute KATLOG. With the MORE program, if you ask for more than a screen worth, you'll be shown a screen worth at a time. Pressing any key (except the CTRL-BREAK combination) will cause the next page to be displayed to the screen. Holding down the CTRL key while pressing the BREAK key will abort KATLOG -- you'll be asked if you want to terminate the batch pro- cedure then. If you answer "Y", the batch procedure will immediately abort. KATLOG 35 PRN Same as KATLOG 35, except output is printed, & the DOS program, MORE.COM is not used. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 33 INTEGRITY ANALYSIS Every once in awhile (perhaps once a month), an integrity analysis should be done. It really takes no work on your part, & doing it while you are out to eat is the easiest way to schedule it into your day. More is said about doing an integrity analysis in a subsection below. There is nothing magic about the database integrity check program. It is an option in the KATLOOK (or KAT -D option) program. First, get inside to KATLOOK's menu choice. Refer to the section, INQUIRING AGAINST THE DBS- KAT CATALOG, if you forget how to invoke KATLOOK. To the following prompts, make the following responses: PROMPT------------------------ RESPONSE COMMENT---------------------- Enter option number: 3 "Process entire database" option Want date range? ENTER Default is "N", the correct choice Suppress console output? ENTER Default is "N", the correct choice Printout desired? ENTER Default is "N", the correct choice Pause for each screen? ENTER Default is "N", the correct choice KATLOOK will thereupon start from the beginning of your database & display every entry in your database. Every single record in every portion of your database will be retrieved. This can take an hour & a half if using a COMPAQ PLUS with 12,500 directory entries & 580 diskettes cataloged. If you have an IBM AT, your response time will be better. A good time to do this, as earlier said, is during eating time. When you come back to your machine then, you'll immediately know if any problem was encountered. If the last two lines displayed show the last entry in your database followed by the successful database close message, then you have a clean database. At this point, you are advised to backup up your database & label it as a "VERIFIED" backup. Do not recycle these backup diskettes until you have done at least another verified backup in the future using another set of diskettes. Once you have done this backup, you no longer need the current hard disk resident KATDB.LOG file. Type: DEL KATDB.LOG & press ENTER. Don't worry, immediately upon doing your next DBS-KAT process, KATDB.LOG will be recreated & start growing again. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 34 TROUBLE SHOOTING TIPS If the information in this section doesn't solve your problem, refer to the accompanying document, entitled "Advanced Database Integrity Analysis Discussion." If that documentation doesn't solve your problem, consider reinstalling DBS-KAT by using the DBS-KAT manual for DOS-inexperienced users. Failing that, if you're a registered DBS-KAT user, use the DBCHECK program to verify your database. If all else fails, fill out and mail Applied Foresight the DBS-KAT problem form. Print out this form typing: KAT -P and pressing ENTER or if that doesn't work by inserting the DBS-KAT software disk in drive A: and doing: Type: C: and press ENTER. Type: A:USQ A:KATBUG.FQM and press ENTER. Type: COPY KATBUG.FRM PRN and press ENTER. Type: DEL KATBUG.FRM and press ENTER. If you are ever aborted from DBS-KAT during the cataloging program, or if the cataloging program processes less than the full number of filenames on a diskette, check the free space on the device holding the work files, KATWORK1.DIR & KATWORK2.DIR. Also, type out these work files & see if the operating system issued any error messages. The message "Exec Failure," or "db_VISTA database error -905- error opening file", may mean that your "FILES=20" statement is either missing or has a lower number in your CONFIG.SYS file. Don't forget to restart your computer after changing your CONFIG.SYS file. The message "db_VISTA database error -4 - invalid database" can appear if the program is not able to find the database. DBS-KAT attempts to open the database in the current directory. Failing that, it attempts to open the database in the \DBSKAT directory for the current drive. Failing that, it attempts to open the database in the root (\) directory for the current drive. If the database can't be found still, it will display the preceeding error message. If the database exists in one of these three directories, the message may still appear if the program you are running is DBCHECK KATDB. (From the DBS-KAT utility disk -- see order form for information on how to obtain.) The DBCHECK KATDB command expects that the DBS-KAT database exists only in the current directory and additionally, that KATDB.H exists in that directory too. (This file comes with the DBCHECK program.) With the message "Bad command or file name" right after the "Do: B,D,E,F,H,L,P,S,T,V,W?" prompt, or the message "error in opening to read A:KATWORK2.DIR" in "KAT -U", verify that the DOS SORT program is in your path. If it isn't, then insert your original DOS diskette in drive A: & type: COPY A:SORT.* \ & press the ENTER key. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 35 ONLINE ASSISTANCE KATBOOK also prints out several other manuals, which should be read. Typing: KAT & pressing the ENTER key will display the commands you can type in to run the various functions of DBS-KAT. Typing: KAT > PRN & pressing the ENTER key will print out the above display. Typing: KAT -O & pressing the ENTER key will print out an order form, along with an explanation of registration benefits. Typing: KAT -P & pressing the ENTER key will print out a problem form which can be used for submitting problems &/or enhancement requests. Typing: KPRINT & pressing the ENTER key will display the features of the KPRINT programmer's print program. Typing: KPRINT -?C>PRN & pressing the ENTER key will print out the above display. Typing: KPRINT -?K & pressing the ENTER key will display how to interface your printer with the KPRINT program. Typing: KPRINT -?KC>PRN & pressing the ENTER key will print out the above display. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 36 APPENDIX A: ERRATA RE: KPRINT PROGRAM Note: for additional information about the KPRINT programmer's print program, refer to the preceeding section, "Online Assistance." Due to the Lattice C Compiler not supporting LPT2 & COM2, KPRINT will not work with either of these two ports. Carl Warren in MINI-MICRO SYSTEMS, April 1985 (page 187), provides a way for your computer to think of LPT2 as LPT1 (and vice-versa) though. A BASIC program, he provides, based upon printer port information discussed in the IBM Technical Reference Manual, pages 5-25, is used to swap printer port locations for the duration of a power-on session. The program is reproduced below: 05 REM DEFINE THE SEGMENT LOCATION 10 DEF SEG = &H40 15 REM FIND THE CONTENTS OF THE PORTS 20 A = PEEK(&H8): B = PEEK(&H9) 30 C = PEEK(&HA): D = PEEK(&HB) 35 REM NOW SWAP THEM 40 POKE &H8,C : POKE &H9,D 50 POKE &HA,A : POKE &H8,B 55 SYSTEM If this program was located in your root directory under the name, SWAPLPT.BAS, & you added the line, "BASICA \SWAPLPT", to your \AUTOEXEC.BAT file, this would be done for you automatically when you power on the computer. If you need to use COM2, use the DOS MODE command to associate COM2 with your LPT1 port. For both the LPT2 & COM2 solution discussed here, your KPRINT.CTL file would use a "T P 1" line. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 37 APPENDIX B: KATSCAN HARD DISK ARCHIVE UTILITY DOCUMENTATION The KATBOOK print procedure printed a four page (80 column printout) on KATSCAN describes the KATSCAN program. Everything described in that doc- ument is on this diskette. This is NOT demo software! DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 38 APPENDIX C: KATASK BATCH MENU FACILITATOR UTILITY DOCUMENTATION KATASK is a simple, short program. The purpose of this program is to facilitate displaying a menu of choices to a user from inside a DOS batch command file. The method of doing this with KATASK is as follows: 1. Inside your DOS batch command file, use the DOS ECHO or REM command to display your menu to a user. Assign a number starting from 1 to each displayed menu line item. 2. After the menu display lines, have a line that reads: KATASK n Substitute for "n", an actual number. This number will be the default menu choice if the user just presses the ENTER key in response to your displayed menu. 3. KATASK reads in the input number & displays the following. In the below example, 3 is the default choice. KATASK requires the user to provide a number. KATASK does not do a numeric value range check. Your DOS batch file must use the IF ERRORLEVEL command to validate an allowable number range. Number of your menu choice? [default=3] => 4. Whatever number is chosen (by default or by entry), KATASK sets the DOS ERRORLEVEL to that number & exits the program. 5. Follow the DOS documentation for the IF ERRORLEVEL command to process the KATASK output. Look at the code in the DBS-KAT batch file, KATBOOK.BAT for a process handling example. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 39 APPENDIX D: PROVIDED DBS-KAT FILES The distribution diskette contains these files: READ ME A short introductory note. To be read first. KATBOOK OQT The compressed DBS-KAT manuals. KATBOOK BAT The DOS Batch process to print manuals. Type: KATBOOK. KATBOOK2 BAT Used by KATBOOK to print manual. Do not execute this. KAT EQE Compressed DBS-KAT program to update control record & catalog diskette directory information into database. KATLOOK EQE Compressed program to allow inquiry against database. KATSCAN EQE Compressed program used by KAT.EXE to scan diskette directory. Also useful hard disk archive utility. KPRINT EQE Compressed multi-feature print program. Made for pro- grammers. KATLOG BAT This & KATSTRIP.BAT are used in maintaining & recovering KATASK COM Program to prompt user for menu choice number. KATSTRIP BAT DBS-KAT. KATSORT BAT Batch file to sort cataloged filenames in reverse chronological order. Use KATLOOK to output a file first. KATORDER FQM Compressed; install first, then type: KAT -O to print this order form. KATBUG FQM Compressed; install first, then type: KAT -P to print this problem report form. KATDB DBD The database comprises this & the next 5 files. KATDB DA1 " ". KATDB DA2 " ". KATDB DA3 " ". KATDB KE1 " ". KATDB KE2 " ". USQ COM This (also known as ALUSQ, by Alan Losoff) & SQ (also known as SQPC, by Vernon D. Buerg) are both public domain programs which allowed the manuals to be compressed & decompressed. SQ.EXE is not provided with DBS-KAT. VOLSER COM This is a device volume labeler program in the public domain written by T. A. Davis. Can be used by DBS-KAT. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 40 APPENDIX E: MINIMUM COMPUTER FILES NEEDED TO OPERATE DBS-KAT An installed DBS-KAT drive volume needs the following files on a drive formatted with the "/S" option. Files marked with a "*" are your DOS operating system files. COMMAND COM * AUTOEXEC BAT BACKUP COM * CONFIG SYS FORMAT COM * KAT EXE KATDB DA1 KATDB DA2 KATDB DA3 KATDB DBD KATDB KE1 KATDB KE2 KATSCAN EXE KATASK EXE KATLOG BAT KATLOOK EXE KATSORT BAT KPRINT EXE MORE COM * RESTORE COM * SORT EXE * VOLSER COM DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 41 APPENDIX F: WHY DOS 2.X USERS SHOULD UPDATE TO DOS 3.2 OR DOS 3.3 With DBS-KAT Version 2.10, users need to upgrade to DOS 3.X. DBS-KAT was developed under MS-DOS 3.10 & tested under it & PC-DOS 3.3. Since DBS-KAT is targeted for fixed disk users, it will greatly benefit you to upgrade to DOS 3.X. Below, I compare what you get with PC-DOS 3.3 that you didn't get with DOS 2.X. What isn't discussed below include the technical reasons DBS-KAT now relies upon DOS 3.X. The new internal DOS functions available under DOS 3.X, which can be read in a DOS 3.X Technical Reference Manual, enabled DBS-KAT to jointly enjoy a performance upgrade & to support foreign users who represent a large portion of the regis- tered users. SELECTED PC-DOS 3.3 MACHINE MANAGEMENT IMPROVEMENTS: PC-DOS 3.3 speeds up screen I/O. Although I haven't seen this documented in print. Myself & everyone who I have talked to, have noticed a sig- nificant speed improvement in screen operations such as DIR & TYPE. Under PC-DOS, all files occupy an amount of space equal to the cluster size that can hold the file size. PC-DOS 3.0 & higher were written to handle disk drives larger than 20 MB. If you create a single byte file under PC-DOS 2.X on a fixed disk, you lost 4,096 bytes on a 10 MB drive, 8,192 bytes on a 20 MB drive, & so on. This is because of PC-DOS 2.X cluster size algorithm based upon it only being used with slow, 10 MB drives. Assume you install DOS 3.0 or higher & you FDISK removed the old DOS 2.X partition & recreated the drive anew starting from a FDISK install. Under PC-DOS 3.0 & higher, with disk drives 20 MB or larger, no matter how large your disk is, a single byte file only looses 2,048 bytes on a disk. Ten MB disk drives retain the same cluster size as under DOS 2.X (4096). Peter Norton wrote that on a 20 MB drive, using DOS 3.X versus DOS 2.X, a user gains about 10 percent in additional disk utilization because of this cluster size difference. Although not an official part of PC-DOS 3.3, IBM & many other vendors are supplying a disk caching software program with their 80286 computers. This allows memory, including memory above 640K, to be used to reduce disk I/O, thereby improving system speed. Disk caching is superior to a RAM disk, because turning a computer off with disk caching does not cause any loss of data & because disk caching speeds up all frequently used files, not just the ones that you predict will be frequently used. SELECTED PC-DOS 3.3 CONFIG.SYS FEATURES: 1. COUNTRY= DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 42 For foreign users. With this, you can customize your keyboard & output to your language. 2. DEVICE= New device drivers (VDISK.SYS, DRIVER.SYS, DISPLAY.SYS) enable users (1) to use a portion of their memory (whether above or beneath 640 K RAM) as a high speed disk drive, (2) to reference one of their floppy disk drives as having two drive letters (even for users who have a drive A: & B:); & (3) support screen displays for IBM EGA & LCD monitors used in certain foreign countries. 3. LASTDRIVE= This clause & the DOS SUBST command allows users to have drives let- tered through Z:. With SUBST, users will often create an alias drive letter substitute for directories which are long to type out (e.g., \WP\MULTIMATE\LIBRARY\LEGAL). 4. SHELL= Additions to this command allows users to create a larger DOS environment space, which then allows long PATH & PROMPT clauses as well as user-defined environment variables. For example, suppose one has this line in their \CONFIG.SYS: SHELL=C:\COMMAND.COM /P /E:500 Then one could easily have a DOS environment (shown by typing: SET & pressing ENTER) as follows: COMSPEC=C:\COMMAND.COM PROMPT $e[s$e[1;55H$e[K$e[41m$e[37m $d $e[40m$e[36m$e[u($p) PATH=E:\;C:\RIGHT;C:\;D:\BAT;D:\UTIL;C:\PCW;C:\DOS;C:\EC;C:\XY; C:\KAT;D:\RBFILES EC=C:\EC LC=D:\DEV SELECTED PC-DOS 3.3 COMMANDS: 1. APPEND APPEND lets you establish a search path for your overlay files, help & data files just as you can do for your executable files with PATH. 2. ATTRIB ATTRIB lets you alter a file's "archive" & "read-only" status. It can also determine the current settings of these attributes. One use is to alter the archive status & affect the operation of the BACKUP command. 3. BACKUP BACKUP now supports (1) backing up files modified since a given date & time (not just date alone); (2) formatting target diskettes if they are not formatted already; & (3) creating a log file (BACKUP.LOG). DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 43 4. CALL CALL allows a batch file to be called from within another batch file without ending the first batch file. 5. FASTOPEN FASTOPEN speeds up directory searches by storing in memory (normally they're stored in files) the location of directories & recently opened files. If you have a long PATH or your directories are large, this will significantly speed up your system. 6. FDISK FDISK now supports creating multiple logical drives within one physical drive. Since DOS is limited to 32 MB drive sizes, this allows DOS to support physical drives larger than 32 MB. 7. GRAFTABL GRAFTABL is used to display foreign language characters when in graphics mode on the color/graphics adapter. 8. GRAPHICS GRAPHICS now supports doing print-screents with more printer types, including color printers. 9. JOIN With JOIN, you can attach a floppy-disk drive to your hard disk as a subdirectory. Typing: JOIN A: C:\NEWDIR creates on drive C a new subdirectory called \NEWDIR yet updates/reads are made against the root directory of drive A. 10. KEYB KEYB remaps your keyboard to support non-US English keyboards. 11. LABEL LABEL allows you to create, change or delete a volume label on a disk. 12. NLSFUNC NLSFUNC provides additional support for extended country information. 13. PRINT PRINT now supports fine tuning of its buffer size, timing parameters, printer port & queue size. DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 44 14. REPLACE REPLACE is an intelligent COPY command. You can elect to replace files if the source files are newer than the target files, replace matching files in all subdirectories on your disk, & replace read- only files. You can use REPLACE to copy only those files that do not exist on the target. You can ask REPLACE to prompt you for each file it wants to process. 15. RESTORE RESTORE now supports (1) restoring files modified on or before a given date; (2) restoring files modified on or after a given date; (3) restoring files modified or deleted since they were backed up; (4) restoring files that no longer exist; (5) restoring only those files that were modified at or later than the given time; & (6) restoring only those files that were modified at or earlier than the given time. 16. SELECT RESTORE installs DOS on a new disk with the keyboard layout, date & time format you select. 17. SUBST SUBST allows one to refer to a directory by using a designated drive letter. This saves typing out long CHDIR (CD) commands. 18. XCOPY XCOPY is a super-powered COPY command, which can include lower level subdirectories. Whereas the DOS COPY command is slow because it works one file at a time (if a file is less than 65,536 bytes large) or in 65,536 byte chunks, the XCOPY command reads all files captured by your fileset argument into memory before writing out to the target. In addition, XCOPY can restrict itself to just copying those files that (1) which have the archive bit of the attribute set to one; (2) have a date the same or later than a specified date. XCOPY can create subdirectories on the target drive; it can turn off the archive bit of the source file; it can prompt you before copying each file; & it can copies files in the current directory or all those beneath it. SUMMARY: THE BEST REASONS TO UPGRADE TO PC-DOS 3.2 or 3.3 Most of the above commands appear in MS-DOS or PC-DOS 3.2. CALL, FASTOPEN, & the new parameters for BACKUP & RESTORE are the significant DOS 3.3 goodies. The best reasons for fixed disk users with DOS 2.X to upgrade to 3.2 or 3.3 are: DBS-KAT USER MANUAL Copyright 1986 R.H. Martin P. 45 -> faster performance (by FASTOPEN, XCOPY, VDISK, disk caching, improved screen I/O); -> better disk & file utilization (by improved FDISK; by smaller cluster size, by less redundant files on disk through APPEND), by better file archiving management through XCOPY, REPLACE, LABEL & the better BACKUP); -> more convenient to use (especially with LABEL, REPLACE, XCOPY, SUBST, SELECT, APPEND, BACKUP & RESTORE, PRINT & CALL); -> more fun (new SHELL clause in CONFIG.SYS supports a larger DOS environment space thereby allowing fancier PATH & PROMPT statements); -> more international; (a multitude of commands support foreign language users). DBS-KAT (R) The Easy, Practical, Super Capacity Diskette Cataloger And Hard Disk Archive Utility INSTALLATION FOR NEW COMPUTER USERS by R.H. Martin Applied Foresight Inc. P.O. Box 20607 Bloomington, Minn. 55420 Nov. 13, 1987 Copyright 1986, 1987 by R.H. Martin All Rights Reserved A DB-SHAREWARE Software Product A limited license is hereby granted to copy and distribute wholly unmodified copies of the DBS-KAT Software Diskette which contains this manual (Read the manual, "THE DB-SHAREWARE PROGRAM" for full details about this limited license) NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 2 ABOUT THIS MANUAL ----------------- A section is designated by a centered & underlined heading. Centered but NOT underlined headings are referred to as a subsection. Absolutely, do not use DBS-KAT prior to thoroughly following the installation instructions, including restarting your computer after following the installation instructions. INSTALLATION ------------ OVERVIEW Installation requires that you configure your operating system environment to satisfactorily accomodate database management processing & that you install the DBS-KAT software on your hard disk. If you are already familiar with PC-DOS or MS-DOS, please follow the two page install instructions in the DBS-KAT general manual. These instructions are for those persons unfamiliar with PC-DOS & MS-DOS. This manual only substitutes for the two page install instructions in the general DBS-KAT manual. Prior to using this manual, you should printout the general manual first & read its section on "Hardware Requirements." After you follow the install instructions given for novices below, read the general manual sections which follow its condensed install instructions. At the end of your installation, you'll end up with some install files that don't need to be on your hard disk. To delete these files & the print process from your hard disk, position your cursor in the same directory on your hard disk where you installed DBS-KAT & type: DEL USQ.* & press ENTER. DEL KATBOOK*.* & press ENTER. DEL *.EQE & press ENTER. DEL *.FQM & press ENTER. DEL READ.ME & press ENTER. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 3 INSTALLATION INSTRUCTIONS FOR THE DOS 3.0+ NOVICE USER Installation requires the following specific acts. It is assumed that your floppy disk drive used is drive A & that your fixed hard disk drive is drive C. Read each step through before you actually following the instructions given during that step. 1. In this step, you will make a directory for DBS-KAT, copy the diskette contents to it, and make a backup copy of your DBS-KAT diskette for archival purposes. You should make a directory for DBS-KAT on your hard disk. What you will be instructed to do is to copy your source diskette (eg, your original DBS-KAT diskette) to this directory on your hard disk. Then you will remove the diskette in drive A & insert a formatted floppy in your drive A, which will be the target diskette to hold your backup copy of DBS-KAT. Type: MD C:\DBSKAT & press the ENTER key. This creates a directory on your hard disk, called "\DBSKAT". Insert your original DBS-KAT diskette in drive A. Type: COPY A:*.* C:\DBSKAT/V & press the ENTER key. This copies everything from drive A to your directory, \DBSKAT. The "/V" causes a verify function to occur throughout the COPY process. Remove your original DBS-KAT diskette from drive A. Insert a formatted diskette in drive A. If you don't know what "formatted" means, refer to your DOS GUIDE TO OPERATIONS manual & look up what the FORMAT command does. Just in case, you are using a previously used diskette with files on it that you don't care about anymore, you should delete these files before using the diskette again. Type: DEL A:*.* & press the ENTER key. You will be asked by the operating system if "Are you sure (Y/N)?". If you are sure that you want these files deleted, type: Y & press the ENTER key. If you didn't have any files on this diskette, you'll receive the message "file not found". Don't worry about this message. Type: COPY \DBSKAT\*.* A:/V & press ENTER. Type: C: & press ENTER. Type: CD \DBSKAT & press ENTER. Leave the floppy diskette in drive A until done with step 2. 2. You now need to decompress & install the DBS-KAT programs that are on the DBS-KAT diskette. You'll install them in the current directory of drive C: (which is \DBSKAT). Type: A: & press the ENTER key. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 4 Type: KATBOOK & press the ENTER key. Choose the option to decompress & install the DBS-KAT programs. Remove the floppy diskette in drive A & label it appropriately. 3. You now need to ensure that everytime you power on, that your system comes up with the right date & time, with its computer environment in tune to your root directory, & that it can handle the extra demands put on it by multi-file processing. In this step, we'll handle the CONFIG.SYS file, which addresses these extra demands. With your prompt positioned on the hard disk, type: CD \ & press the ENTER key. This moves you to the root directory, if you are not already there. You may or may not have a CONFIG.SYS file. Type: DIR CONFIG.SYS & press the ENTER key. A)If you get the message "File not found", type the following lines: Type: ECHO FILES=20 > CONFIG.SYS & press the ENTER key. Type: TYPE CONFIG.SYS & press the ENTER key. You should see the below: FILES=20 If you don't see the above, redo this step again. Go to step 4 now. B) If you got a display with the bottom line starting out as "1 file(s)...", type: TYPE CONFIG.SYS & press the ENTER key. If you don't see a line that start out with "FILES=", type the following lines: Type: COPY CONFIG.SYS CONFIG.SAV & press the ENTER key. Type: ECHO FILES=20 >> CONFIG.SYS & press the ENTER key. Type: TYPE CONFIG.SYS & press the ENTER key. You should see the below [you may see other lines than the below in your CONFIG.SYS file]: FILES=20 If you don't see the new line, perform the following recovery steps: Type: COPY CONFIG.SAV CONFIG.SYS & press the ENTER key. Now redo the above ECHO command followed by the TYPE command. You can erase your backed up CONFIG.SYS file, type: DEL CONFIG.SAV & press the ENTER key. Now go to step 4. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 5 C) If you did see a line that start out with "FILES=", you'll have to use an editor of some sort which can work with plain ASCII files. If you don't understand this last, sentence, then just follow the instructions here. We'll use the DOS freebie editor, EDLIN.COM. Make sure you have copied this program onto your hard disk from your original DOS diskette. Study the sample editing session shown on the next page before being given specific instructions: =============================================================== ACTUAL COMPUTER INPUT/OUTPUT Ref Line # ----------------------------------------------- ---------- >COPY CONFIG.SYS CONFIG.SAV A 1 File(s) copied >TYPE CONFIG.SYS B BREAK=ON FILES=20 DEVICE=ANSI.SYS >EDLIN CONFIG.SYS C End of input file *L D 1:*BREAK=ON 2: FILES=10 3: DEVICE=ANSI.SYS 4: *2 E 2:*FILES=10 F 2:*FILES=20 G *L H 1: BREAK=ON 2:*FILES=20 3: DEVICE=ANSI.SYS 4: *E I >TYPE CONFIG.SYS J BREAK=ON DEVICE=ANSI.SYS FILES=20 >DEL CONFIG.SAV K ============================================================== Because your CONFIG.SYS file may have a different number of lines in it than the one shown, you'll have to modify it following the principles documented here, rather than blindly following instructions. To aid you, you'll be given an overview of what occurred above. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 6 Line A shows the user typing the entire line following the prompt symbol ">". This is done for backup, safety purposes. You should perform this line as shown. Line B shows the user looking at the CONFIG.SYS file prior to entering into an EDLIN editor session. You can do this also if you want to. Line C shows the user invoking the EDLIN editor program against the file CONFIG.SYS. You should perform this line as well as Line D as shown. Line D lists the file to the screen. The output is the same as that of Line B, except that line numbers appear now. Line E shows the user typing this line number, corresponding to the "FILES=" statement & pressing the ENTER key. Using the appropriate line number, you should do this as well. Line F & the "2:*" of line G are shown in return, & the user's cursor is positioned to the right of the "*". Line G shows the user typing "FILES=20" & pressing the ENTER key. Using the appropriate line number, you should do this as well. Line H shows the user relisting the edited file. Line I shows the user ending the EDLIN editor session, which saves his changes to the disk & exits him back to the DOS level. Line J shows the user retyping the CONFIG.SYS file back to the screen. This confirms that the file was edited correctly. Line K shows the user deleting the unused backup file. 4. You still need to ensure that everytime you power on, that your system comes up with the right date & time, with its computer environment in tune to your root directory and at least the DBSKAT directory. Similarly to how we handled the CONFIG.SYS file, we'll now handle the AUTOEXEC.BAT file, which can be made to ensure all these things. First, you are recommended to read the section in your DOS manual about "PATH". Regardless of whether you have a system clock, which you'll have if you have an IBM AT, you'll be recommended to include in your AUTOEXEC.BAT file DATE & TIME statements. This is because your clock can get off for several reasons, & being reminded of the current date & time upon each power-up is good practice. For sure, your clock will be off when you change to/from daylight savings time or when your clock battery gets weak. In addition, although it is not required, since it is a nice enough feature to include, you'll be shown a way to modify your system prompt to always remind you of where you are at on the hard disk. The PROMPT ($P) line will change your system prompt from a ">" to a "(C:\)" instead. If you happen to be in a created NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 7 directory that you might have for some other purpose, such as \WP (for your word processor), you'll see your prompt like this: "(C:\WP)". You may or may not have a AUTOEXEC.BAT file. Type: DIR AUTOEXEC.BAT & press the ENTER key. A) If you get the message "File not found", type the following lines: Type: ECHO PATH=C:\;C:\DBSKAT > AUTOEXEC.BAT & press the ENTER key. Type: ECHO DATE >> AUTOEXEC.BAT & press the ENTER key. Type: ECHO TIME >> AUTOEXEC.BAT & press the ENTER key. Type: ECHO PROMPT ($P) >> AUTOEXEC.BAT & press the ENTER key. Type: TYPE AUTOEXEC.BAT & press the ENTER key. You should see the below: PATH=C:\;C:\DBSKAT DATE TIME PROMPT ($P) If you don't see the above, redo the four ECHO lines, & don't forget one greater-than sign on the first line & two greater- than signs on the following lines. Go to step 5 now. B) If you got a display with the bottom line starting out as "1 file(s)...", type: TYPE AUTOEXEC.BAT & press the ENTER key. If you don't see any lines that start out with "PATH", "DATE", "TIME" & "PROMPT", type the following lines: Type: COPY AUTOEXEC.BAT AUTOEXEC.SAV & press the ENTER key. Type: ECHO PATH=C:\;C:\DBSKAT >> AUTOEXEC.BAT & press the ENTER key. Type: ECHO DATE >> AUTOEXEC.BAT & press the ENTER key. Type: ECHO TIME >> AUTOEXEC.BAT & press the ENTER key. Type: ECHO PROMPT ($P) >> AUTOEXEC.BAT & press the ENTER key. Type: TYPE AUTOEXEC.BAT & press the ENTER key. You should see the below [you may see other lines than the below in your AUTOEXEC.BAT file]: PATH=C:\;C:\DBSKAT DATE TIME PROMPT ($P) If you don't see the new lines, perform the following recovery steps: NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 8 Type: COPY AUTOEXEC.SAV AUTOEXEC.BAT & press the ENTER key. Now redo the above ECHO commands followed by the TYPE command. Don't forget to use two greater-than signs for each ECHO command line. You can erase your backed up AUTOEXEC.BAT file, type: DEL AUTOEXEC.SAV & press the ENTER key. Now go to step 5. C) If you did see lines that start out with "PATH", "DATE", "TIME", or "PROMPT", you may have to use an editor of some sort which can work with plain ASCII files. If you don't understand this last, sentence, then just follow the instructions here. We'll use the DOS freebie editor, EDLIN.COM. Make sure you have copied this program onto your hard disk from your original DOS diskette. Study the sample editing session shown on the next page before being given specific instructions: NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 9 ============================================================== ACTUAL COMPUTER INPUT/OUTPUT Ref Line # ------------------------------------------------ ---------- >COPY AUTOEXEC.BAT AUTOEXEC.SAV A 1 File(s) copied >TYPE AUTOEXEC.BAT B PATH=C:\DOS VERIFY ON CHKDSK /F >EDLIN AUTOEXEC.BAT C End of input file *L D 1:*VERIFY ON 2: PATH=C:\DOS 3: CHKDSK /F 4: *2 D E *L F 1: VERIFY ON 2:*CHKDSK /F 3: *I G 2:*PATH=C:\;C:\DOS;C:\DBSKAT H 3:*DATE I 4:*TIME J 5:*PROMPT ($P) K 6:*^Z L *E M >TYPE AUTOEXEC.BAT N VERIFY ON PATH=C:\;C:\DOS;C:\DBSKAT DATE TIME PROMPT ($P) CHKDSK /F >DEL AUTOEXEC.SAV O ============================================================== Because your AUTOEXEC.BAT file may have a different number of lines in it than the one shown, you'll have to modify it following the principles documented here, rather than blindly following instructions. To aid you, you'll be given an overview of what occurred above. You should first be forewarned that you might have an AUTOEXEC.BAT which "chains" to other ".BAT" files. If so, then it is very important that you have an experienced DOS user modify your AUTOEXEC.BAT correctly. Chances are that your NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 10 AUTOEXEC.BAT file is not engaged in chaining operations, & the below instructions should suit you adequately. If you are curious whether a particular line is a command to chain to another .BAT file, you can verify your hunch in the following manner. Pretend a line in your AUTOEXEC.BAT file reads "MENU". To find out if this is a command to chain to a .BAT file or if it is invoking a program, type: CHKDSK/V | FIND "MENU." & press the ENTER key. If all you see in response (which might be 2-3 minutes) is something like this, "C:\UTIL\MENU.BAT", you can bet that AUTOEXEC.BAT will do a chain operation when this line is executed, meaning that no entries following this line will be executed if the chain line is executed. Again, if you suspect chaining to another .BAT file occurs in your AUTOEXEC.BAT file, you are recommended to seek the help of an experienced DOS user to modify your AUTOEXEC.BAT correctly. Line A shows the user typing the entire line following the prompt symbol ">". This is done for backup, safety purposes. You should perform this line as shown. Line B shows the user looking at the AUTOEXEC.BAT file prior to entering into an EDLIN editor session. You can do this also if you want to. Looking at this AUTOEXEC.BAT file, one can see that is lacks a "DATE", "TIME", & "PROMPT" statement. However, this AUTOEXEC.BAT does have some nice safety features in it. Notice that it does a CHKDSK /F for the user automatically upon power up. It also causes the DOS COPY VERIFY function to always work, regardless of using the "/V" on the DOS COPY command. You may also want to consider adding these two AUTOEXEC.BAT commands as well. You aren't required to by DBS-KAT though, just as you aren't required to use a special PROMPT. It's just that using these features can make your hard disk operations cleaner. The "PATH" line shown under Line B is inadequate for the only directory pointed to in it is the directory called "C:\DOS". For example, if the line read "PATH=C:\;C:\DOS;C:\DBSKAT", "PATH=\;\DOS;\DBSKAT", or "PATH=\DOS;\;\DBSKAT", the "PATH" line would be correct. One does not need the "=" sign, in place of it could be a blank space. One can also have a semicolon ";" at the end of the line with no harm. What is wrong about the "PATH" statement shown by Line B's action is that the root directory "\" or "C:\" and the "\DBSKAT" or "C:\DBSKAT" directory is not in the PATH. The literal "C:\DOS" refers to the subdirectory "\DOS". If everything looks correct in your AUTOEXEC.BAT, you can proceed to Step 5 now. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 11 Line C shows the user invoking the EDLIN editor program against the file AUTOEXEC.BAT. You should perform this line as well as Line D as shown. Line D lists the file to the screen. The output is the same as that of Line B, except that line numbers appear now. You should note the first line number alongside the "PATH" statement. If you see a "PROMPT" statement, then you already know enough about it to have it already tailored to your needs & you might as well leave it as you already have it. If you see a "DATE" or "TIME" statement, then you don't need to delete it & then re-enter it. Leave these two statements where they lay. Line E shows the user deleting the old entry for the "PATH" statement. Using the appropriate line number, you should do this as well. Line F shows the user relisting the edited file. Note the re-arranging of the line numbers. Line G shows the user preparing to insert the lacking statements. If you already have a "PATH" line, but it doesn't include reference to the root directory, then retype a "PATH" line like the old, but with reference to the root directory in it, as shown in this example. Lines H through K show the actual insertion lines. Line L shows the user ending the insertion process by pressing the F6 function key followed by an ENTER key. You'll have to do this as well. Line M shows the user ending the EDLIN editor session, which saves his changes to the disk & exits him back to the DOS level. Line N shows the user retyping the AUTOEXEC.BAT file back to the screen. This confirms that the file was edited correctly. Line O shows the user deleting the unused backup file. 5. You should restart your computer now. You will now benefit from the changes made above. 6. Make sure that you have the following DOS programs loaded onto your hard disk: FORMAT, SORT, BACKUP, RESTORE & MORE. These programs are DOS programs which DBS-KAT expects to be able to run, if you choose the option which uses them. (Don't worry about the FORMAT command & your hard disk. DBS-KAT only allows you to FORMAT drive A or drive B.) Chances are you have these programs already installed in a \DOS directory or your root directory. If you don't have these programs on your hard disk, insert your original DOS diskette in drive A: & type the following commands: COPY A:FORMAT.* C:\ /V & press ENTER. COPY A:BACKUP.* C:\ /V & press ENTER. COPY A:RESTORE.* C:\ /V & press ENTER. COPY A:SORT.* C:\ /V & press ENTER. COPY A:MORE.* C:\ /V & press ENTER. 7. Hopefully you have done this before this, but to be safe, we will verify that your equipment meets the recommended requirements listed under the "HARDWARE REQUIREMENTS" section. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 12 First, you should have an IBM or compatible type personal computer. This product was developed on a COMPAQ PLUS and Heathkit Z-241 AT Compatible, so it definitely runs on an IBM compatible type computer. Next, you need to have the correct version of either the PC-DOS or the MS-DOS operating system. Type: VER & press the ENTER key. The N.NN number which appears on the far right hand side of the displayed line should be greater than or equal to 3.00. If it is, & you either see the phrase "PC-DOS" or "MS-DOS", then you have a supported operating system environment. The current version of DBS-KAT was developed under MS-DOS 3.10. Next, you need to know about your hard disk & available user memory. Type: CHKDSK C: & press the ENTER key. If you get the message "Bad command or file name", you should put your original DOS diskette in drive A & type: A:CHKDSK C: & press the ENTER key. If the program asks you for a "Y" or "N", go ahead & answer "N" for the time being. When you get the prompt back, you might want read up in your DOS manual about the CHKDSK program. Then you should consider rerunning the command in the following manner. Type: CHKDSK C:/F & press the ENTER key. When given the "Y" or "N" prompt, answer "Y" this time. Then you might want to type out the files, "C:\FILE0???.CHK". You should seek expert advice about what these file displays mean. Once satisfied, you could then delete these files "C:\FILE0???.CHK". The number that appears alongside the CHKDSK phrase "bytes total disk space" should be at least a 7 or higher digit number, indicating that you intend to run your software either on a high capacity 1.2MB floppy or, preferrably, on a hard disk (in which case, you'll have a 8 or higher digit number). The number that appears alongside the CHKDSK phrase "bytes available on disk" should indicate at least 500,000 (or 0.5 MB), for with the software & even a small DBS-KAT database (after a month's usage), you'll be using up at least this much disk space. Covering 500 diskettes & 10,050 filenames, will require about 925,000 bytes (or 0.925 MB). This 0.925 MB figure includes the DBS-KAT software space requirements. Make sure you have adequate disk space before doing DBS-KAT install. The number that appears alongside the CHKDSK phrase "bytes free" indicates available user memory (RAM available). You are advised to have at least 262,144 bytes of RAM or 256K RAM free before running DBS-KAT. DBS-KAT may run slightly under that amount of RAM free space, but you do so at your own risk. NOVICE INSTALL MANUAL Copyright 1986 R.H. Martin P. 13 8. Go to paragraph 7 in the USER MANUAL, under the subsection entitled "SHORT INSTALLATION INSTRUCTIONS FOR THE DOS 3.0+ EXPERIENCED USER", in the section on "INSTALLATION." OVERVIEW: DBS-KAT (R) - THE COMPLETE FILE LIBRARIAN DB-SHAREWARE PACKAGE The Easy, Practical, Super Capacity Diskette Cataloger And Hard Disk Archive Utility by Applied Foresight, Inc. P.O. Box 20607 Bloomington, Minn. 55420 (C) Copyright 1986-1989 R.H. Martin. All Rights Reserved. DBS-KAT is a DB-SHAREWARE product which means the basic, full-featured, system disk can be freely shared with other users. For more information about DB-SHAREWARE, a manual introducing the program is on the system disk for you to print out. DBS-KAT is for 320 KB RAM computers which have at least PC-DOS or MS- DOS 3.00 or greater and have a hard disk. DBS-KAT BASE SYSTEM FEATURES OVERALL FEATURES: * Accomodates 9,999 diskettes containing up to 16 million filenames in one central database. * Accomodates cataloging removeable disk cartridges. * Filenames cataloged without any data entry required. * Designed to meet the cataloging needs of hard disk owners. * Enables hard disk owners to consider their diskettes an extension of their hard disk subdirectories. * Condensed online help screen. * Feature-rich programmer source code print program included (KPRINT). * Useful hard disk archive utility program included (KATSCAN). * Useful batch file utility program to facilitate menu-driven operations included (KATASK). * Thorough documentation, including recovery documentation & a manual for both DOS novices & advanced users. * Version 2.10 & greater reads the volume label in such a way as to support non-USA PC/MS-DOS versions. CATALOG UPDATING FEATURES: * Add or change a 4 digit diskette volume label within program. * Embedded volume labels of any length/format can be retained. User must assign a logical 4 digit diskette volume ID to associate w/diskette. * Optionally create unique header record for each cataloged diskette. * Diskette header carries freespace and filesum number for each diskette without any user entry involved. * Allows user-created default answers to diskette header fields, which can be changed or over-ridden. * Files located in diskette subdirectories are automatically cataloged. * Allows directory lists, deletes, or format of diskettes within program. * Allows a database backup while in the program. * Switch to cataloging another diskette drive or removeable disk cartridge while in the program. * Empty diskettes are specially processed as scratch diskettes. * Optimized for speed, written in C using DB_VISTA database manager. * Recognizes a previously cataloged, unchanged diskette, informs the user and bypasses recataloging. * Optional support for RAM disk utilization for program work files. * Uses file compression techniques. * Maintains a log file of 4 digit volume IDs processed, which can aid database recovery if the database is ever damaged. CATALOG INQUIRY FEATURES: * Password required to view contents of database, --database owner can change this password (i.e., 2 passwords: user's & owner's). * Lists all database filenames or diskette header records, or subsets of either. * Can list diskettes by volume ID order or by descending free space order. * Can list diskettes whose header record meets the selection criteria given by user. * Provides list of scratch diskettes. * Easy method to list what diskettes hold backups of DBS-KAT database. * Diskette list shows the previous & following diskette volume for a multi-diskette set. * Identifies BACKUP or other type volume. * Lists uncataloged diskette numbers available. * Selection can be by exact or partial match. * User's search phrase can be exact length or be a left justified phrase or floating phrase. * Selection can include the filename, file extension, comment information, a beginning/ending filedate range, &/or directory location (if contained in a directory on the diskette). * Retrieval can be limited to entries cataloged at home, work or at both locations. * Listings can be directed to the screen, printer or file. * Listings can be interrupted by pressing the ESC key. * Screen listings pause until any key is pressed. * Listings carry a date/time stamp and headings. * Retrieval list can be sorted in reverse chronological order or user- modified to sort on any desired field. TO USE DBS-KAT Insert the DBS-KAT diskette in drive A:. Then type the following: TYPE A:READ.ME and press the ENTER key. Follow the instructions given to print out the DBS-KAT user manuals. The manuals have install & usage instructions. NOTES DB_VISTA is a trademark of RAIMA Corporation, 12201 SE Tenth St., Bellevue, WA 98005 DBS-KAT was originally released under the name, PC-KAT. EVERYTHING DESCRIBED HERE IS ON THE ENCLOSED DISKETTE. THIS IS NOT DEMO SOFTWARE! DBS-KAT (R) The Easy, Practical, Super Capacity Diskette Cataloger And Hard Disk Archive Utility TECHNICAL REFERENCE MANUAL by R.H. Martin Applied Foresight Inc. P.O. Box 20607 Bloomington, MN 55420 April 1, 1989 Ver. 2.20 Copyright 1986, 1987 by R.H. Martin All Rights Reserved A DB-SHAREWARE Software Product A limited license is hereby granted to copy & distribute wholly unmodified copies of the DBS-KAT Software Diskette which contains this manual (Read the manual, "THE DB-SHAREWARE PROGRAM" for full details about this limited license) DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 2 TABLE OF CONTENTS Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Efficiency Of DBS-KAT. . . . . . . . . .. . . . . . . . . . . . . . . . 3 DBS-KAT Inquiry Search Strategies . . . . . . . . . . . . . . . . . . . 5 Recovering Your Database. . . . . . . . . . . . . . . . . . . . . . . . 7 Upgrading A PC-KAT/Pre-2.0 DBS-KAT Database . . . . . . . . . . . . . . 9 DBS-KAT Version History . . . . . . . . . . . . . . . . . . . . . . . .11 ABOUT THIS MANUAL With the exception of the Registration Benefits section, this manual restricts itself to the base DBS-KAT software diskette. The concept of "base software" is discussed in greater detail in the THE DB-SHAREWARE PROGRAM manual. A section is designated by a centered & underlined heading. Centered but NOT underlined headings are referred to as a subsection. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 3 EFFICIENCY OF DBS-KAT DBS-KAT is fast & efficient, minimizing the amount of disk space required to store the cataloged information. Each date & time field is con- catenated together & stored as a 4 byte long integer. In plain words, what you see on the screen as 10 bytes of information is stored in 4 bytes of storage. The four byte volume ID is stored as a 2 byte integer. If a diskette filename is associated with a floppy subdirectory, the directory name is separately stored in the database only once in its alphabetical description form, & given an ID number. This ID number is carried in the appropriate individual filename records. The entire DBS-KAT database is kept in the files prefixed as KATDB.DA & KATDB.KE. The database contains the system control record, the diskette volume text information & the directory file information for all cataloged files. In addition, all the record pointers are stored in the database to allow quick updating & retrieval of information. The file KATDB.DBD is the data base structure dictionary which never grows but is needed for the programs to work & must reside in the same directory area on the hard disk alongside the other KATDB files. What this means is that although DBS-KAT must keep its inter- relationships connected at the disk drive level versus smaller packages which do most of their inter-relationships at runtime in memory, DBS-KAT does not use up hardly any more disk space, & that is because of its efficient use of disk space. Additionally, DBS-KAT has to allow for its database pointers to expand up to 16 million records. What this means is that on the average, DBS-KAT uses up only 7 percent more space per cataloged directory entry than does its competitors. The other packages gain their processing efficiency by storing the entire database in memory at run time. That is why they can't get larger, because they are constrained by available program data memory space. Yet, without significantly sacrificing additional disk space, DBS-KAT uses disk space to hold its pointers, & achieves comparable processing efficiency on a catalog database capable of holding 16 million records. The author maintains for himself a DBS-KAT database of over 18,000 filenames & around eight hundred diskettes. Throughout the built-up of this database, the author has not noticed a worsening of processing performance, except that a display request for a floating substring phrase within any & all cataloged filenames does take a little longer as the database grows. To use the DOS DIR command syntax to explain this type of search request, although DOS does not honor such a search request, if it did, a request might look like this: DIR *CAT*. On a COMPAQ PLUS, with 8,000 filenames in a DBS-KAT database, it takes under 2 minutes for such a search to finish, whereas with 6,000 filenames, it takes under 1.5 minutes. Search requests for left-hand anchored substring phrases within any & all cataloged filenames is extremely rapid, taking only a couple of seconds to fulfill. A search request at the DOS DIR level might look like: DIR CAT*. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 4 DBS-KAT is fast because of the tools used in developing DBS-KAT (dis- cussed earlier) & because of its streamlined design. For instance, if you have a diskette previously cataloged by DBS-KAT, when you change, add or delete a few files on the diskette, DBS-KAT concentrates on these mod- ifications. A less efficient design might start out the processing of each diskette with the deletion of all prior database information for that diskette. Because of DBS-KAT's usage of the sophisticated DB-VISTA database manager, it is able to immediately access prior information for the at-hand diskette in the correct processing order in which it needs it. Finally, DBS-KAT is fast because it allows the user to use a RAM disk emulator to store the subprograms & work files for DBS-KAT on the RAM disk. DBS-KAT is also fast because it is smart. If you mistakenly insert a diskette which hasn't changed since it was last processed by DBS-KAT, you are told this is the case. DBS-KAT keeps for each diskette both a numeric total of the number of files on the diskette plus the sum of all dates + all times + all file sizes of all the files on the diskette. Before DBS-KAT considers updating directory entries for a diskette, it compares these two new totals with the prior run's old totals. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 5 DBS-KAT INQUIRY SEARCH STRATEGIES To understand the many ways you can search your DBS-KAT database & how efficient will be your search, you need to know how your DBS-KAT database is structured. For searching purposes, you can think of the database being ordered in two different ways: (a) by alphabetical, indexed, order by FILENAME.EXT, regardless of the volume ID; & (b) by numeric, indexed, order by volume ID, & within volume ID order, subordered alphabetically, by FILENAME.EXT. The path information is carried in the database, but it has no ordering effect in terms of aiding retrieval of information. Based upon the structure of DBS-KAT's database design, the following examples represent a range of searchs ordered by a most efficient search argument to a least efficient search argument: FILENAME ARGUMENT TYPE EXT ARGUMENT TYPE PATH/NOTE ARG TYPE -------- - --- - -------- - MYFILE E DOC E MYPATH E MYFILE E DOC E MY A MYFILE E DOC E AT U MYFILE E D A <left blank> MYFILE E O U <left blank> MYFILE E <left blank> <left blank> MY A DOC E MYPATH E MY A DOC E MY A MY A DOC E AT U MY A D A <left blank> MY A O U <left blank> MY A <left blank> <left blank> FIL U DOC E MYPATH E FIL U DOC E MY A FIL U DOC E AT U FIL U D A <left blank> FIL U O U <left blank> * FIL U <left blank> <left blank> ** <left blank> DOC E MYPATH E <left blank> DOC E MY A <left blank> DOC E AT U <left blank> D A <left blank> <left blank> O U <left blank> <left blank> <left blank> MYPATH E <left blank> <left blank> MY A <left blank> <left blank> AT U Don't be afraid to use the search strategy you need to accomplish the job you want done. For instance, against a database of 12,000 directory entries, to search using an argument like the above line with an asterick preceeding it, took around two & a half minutes. This search argument DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 6 causes the entire database keyfile to be scanned from start to end. The last three searches are the most disk intensive types of searches, as they cause the entire database keyfile and datafiles to be scanned from start to end. Search strategies beginning with the double astericked line are sig- nificantly slower than those above it. These search strategies involve intensive disk accessing. That is because both the key and data record must be read from disk for every database record in order to be con- sidered for retrieval. For search strategies before the double- astericked line, the data record was hardly ever accessed if at all. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 7 RECOVERING YOUR DATABASE "Into each life a little rain must fall." It can happen to one's database too. Recovery should be done when you loose your hard disk or when something has damaged your database. In either case, the database recovery procedure is the same. True, you have to restore everything else in a hard disk failure, but you're on your own to figure that dilemna out. Just the database recovery procedure is documented here. Follow these procedures. # ACTION EVENT OR COMMAND COMMENT -- ------ ---------------------------------- ----------------------- 1 Type C: Move to your hard disk. 2 Type CD \ Move to the root directory. 3 Type VERIFY ON Ensure better file copies. 4 Type COPY KATDB.LOG KATDB.FIX Save current log file. 5 Type KATLOG Print your current log file. 6 Find Latest DBS-KAT database backup disks Insert disk 1 into drive. 7 Type RESTORE A: C:KATDB.* Restore old DBS-KAT database. 8 Do DBS-KAT Integrity Analysis if not If integrity fails go using a "VERIFIED" backup set. back to step 5. 9 Read KATLOG printout for line # of B/U state which you're restored to. Call this number "RESTORE-LINENUM". 10 Read KATLOG printout for last line # of printout. Call this number "LAST-LINENUM". 11 Calc Write down what LAST-LINENUM minus RESTORE-LINENUM equals. Call this number STRIP-LINENUM. 12 Type KATSTRIP STRIP-LINENUM Substitute real number. KATDB.FIX now contains an unsorted list of disks to reprocess. 13 Type SORT <KATDB.FIX >PRN This printout is sorted by yet-to-redo volume ID within location. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 8 14 DO KAT -U or some variation Reprocess listed dis- kettes. 15 Type DEL KATDB.FIX No longer needed. You're done! Consider doing a DBS-KAT Integrity Analysis & Backup to preserve the recovery work you just went through. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 9 UPGRADING A PC-KAT/PRE-2.0 DBS-KAT DATABASE Raima Corporation, the developer of DB_VISTA, which is the database manager used by DBS-KAT, found some rare occurring problems with 2.10 of DB-VISTA, which was used for PC-KAT and pre-2.0 versions of DBS-KAT. DB- VISTA release 2.11 and 2.21 was released to fix rare occurring problems. These problems were so rare under 2.10, that I never noticed anything amiss except once after processing 18,000 filenames and nearly 900 dis- kettes. I never noticed anything wrong with DB_VISTA 2.11. DBS-KAT releases as of 2.0 use DB_VISTA 2.11. DBS-KAT releases as of 2.20 use DB_VISTA 2.21. Aside from updated programs, there is not database update requirement going from DBS-KAT 2.0 through 2.10 up to DBS-KAT 2.20. For pre-2.0 DBS- KAT databases, there are two ways to upgrade your existing database: 1. Send $6.50 US (foreign users add $10 US) to Applied Foresight, Inc. for a diskette with a DB_VISTA database rebuild program and a DB_VISTA database consistency checkout program, along with instructions on how to use them. This approach costs money but involves no manual re-entry of database information. Use the KAT -O option to printout an order form to place your order. OR ELSE 2. Build up from scratch a brand new, post-release DBS-KAT 2.X database. To do this, follow the steps below. If you have less than 100 diskettes, you'll find that this isn't all that bad of a task and it will save you the money to pursue option 1. Option 1 however will provide you with a database rebuild program (KEYBUILD) and consistency checkout program (DBCHECK) which is fast and thorough, as they were written by the developers of DB_VISTA. With these programs, you can forever more bypass the DBS-KAT specific integrity analysis procedure, which is not as thorough as DB_VISTA's DBCHECK program. Raima corporation has authorized Applied Foresight Inc. to offer these programs to its customers. To perform step 2, you need to perform the following steps: # ACTION EVENT OR COMMAND COMMENT -- ------ ---------------------------------- ----------------------- 1 Type C: Move to your hard disk. 2 Type CD \ Move to the root directory if DBS-KAT was installed there, else move to the directory where DBS-KAT resides. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 10 3 Type VERIFY ON Ensure better file copies. 4 Type KATLOOK -M Look at your existing System Control Record setup information and using the PrtSc key, record how it is already setup. 5 Type KATLOOK Print out a list of the cataloged volumes that you already have, along with their des- cription. 6 Choose option 4 & have it go to P(rinter) To get a "Listing of cataloged diskette volumes" of your pre- 2.0 DBS-KAT database. 7 DO Delete all old DBS-KAT or PC-KAT files off your hard disk. (Do not undo nor delete whatever is in CONFIG.SYS or your AUTOEXEC.BAT files; nor should you delete whatever DOS pro- grams were needed to work with your old DBS-KAT.) For example, in the directory where you previously installed DBS-KAT, type: DEL KAT*.* 8 Insert DBS-KAT 2.X diskette in drive A:. 9 Follow DBS-KAT 2.X manual instructions to install DBS-KAT. 10 Type: KATLOOK -M Update your System Control Record similar to your old one, as given by the Print Screen done above under step 4. 11 Type: KAT -U Process every diskette listed under step 6 above. Update the volume header database record for each dis- kette with the printout information. 12 You're done! Consider backing up this database now. Back up the database from inside KAT -U program with the "B" option. DBS-KAT TECH REF MANUAL Copyright 1986 R.H. Martin P. 11 DBS-KAT VERSION HISTORY REL. CATEGORY CHG. WHEN COMMENT------------------------------------- 1.0 BETA RELEASE 6/85 Not released to general public. 1.1 BETA UPDATE 6/85 " ". 1.2 PUBLIC REL. 1/86 First public release under PC-KAT name. 1.2A RARE BUG FIX 1/86 If diskette had multiple directories on it, 1.2 occassionally would abort. 1.2B RARE BUG FIX 1/86 Improvement upon 1.2A fix; changing all copyright statements to 1986 year. 1.2C COSMETIC FIX 2/86 KATLOOK handled printer formfeed wrong when doing multi-page volume header subselection retrieval; added version history notes; shortened novice install instructions. 1.3 NAME CHANGE 2/86 Product renamed DBS-KAT. 1.3A NAME CHANGE & 3/86 DB-SHARE concept renamed DB-SHAREWARE & UPD.ENHANCE. Improved support for cataloging remove- able disk cartridges. 1.3B UPD.ENHANCE. 4/86 Support cataloging non-std disk labels. 1.4 INQ.ENHANCE. 5/86 Support inquiry against ext.path/note field. 1.4A COSMETIC CHG 5/86 If DB not in root but present, don't CD \. 2.0 DB_VISTA UPD & 7/86 Update from 2.1 to 2.11 DB_VISTA. Added new ADDED KATSCAN programs, KATASK & KATSCAN, & updated KPRINT. 2.01 SRCH BY SUBDIR 2/87 Allow KATLOOK to search by user providing subdirectory name if cataloged file resides in a subdirectory. 2.02 COSMETIC FIX 4/87 Recognize IAMNOTAN.IBM in curr. or \ dir. 2.10 SEVERAL CHGS 7/87 Converted from Lattice C, Ver. 2.15 to 3.10; DOS 3.X required now; Reads vol. label directory directly, so European DOS users should be supported now; Support installation of DBS-KAT in \DBSKAT subdirectory; & returns user to original subdirectory when done. 2.20 DBMS/C UPDATE 1/89 Update to Lattice 3.21 & DB_Vista 2.21; does not affect database structure; should reduce occurrences of database corruption. Also 2 new capabilities added to option 3 of KATLOOK. DBS-KATr DATABASE INTEGRITY by Applied Foresight, Inc. P.O. Box 20607 Bloomington, Minn. 55420 (C) Copyright 1986 R.H. Martin. All Rights Reserved. TM pending January 6, 1989 To DBS-KAT users: Several user letters have conveyed an interest in or concern about the integrity of their DBS-KAT database. The database manager used by DBS- KAT is DB_VISTAtm by RAIMA Corporation, Bellevue, Washington. It is a very solid database manager and the current release used by Applied Foresight is 2.21. There are no known bugs with this release. Under very rare circumstances, a prior version (2.11 used in DBS-KAT 2.0 through 2.10), could theoretically cause a problem. No known problems with DBS-KAT users were ever known to occur however. Something to be aware of, however, is a documentation shortcoming in older DBS-KAT's manuals. One should not run the DBS-KAT integrity check routine in the KATLOOK or KAT -D (two ways to accomplish the same thing), without first cataloging a diskette (or removeable cartridge). Performing this routine on an uncataloged database results in the message: "db_VISTA database error -19 - record not legal member of set. d_setmr failed in c_dirline for CTRL01. DB status = -19." The database is okay. It just needs at least one volume cataloged first. [Note: if one get this message after cataloging one volume, check if the database was installed in two places on the computer (eg, in \ and \KAT). Perhaps the cataloged volume was added to the database in one directory and the analysis was done on the database in the other directory. With the current release of DBS-KAT, the author has not been able to generate the -19 error message except on a database with no cataloged volumes.] There was a rare occurring bug in versions prior to 2.11 of DB-VISTA and users of DBS-KAT before release 2.0 are advised to follow the advise given in the release 2.0 DBS-KAT Technical Manual. (It is okay to update from a pre-2.0 version to 2.20 and bypass 2.10 of DBS-KAT.) If you used DBS-KAT prior to release 2.0, did you follow those instructions explicitly? This document stated that you were basically given two routes to go to update your database: (1) purchase for $6.50 the DB_VISTA database utilities (DBCHECK and KEYBUILD) and follow Applied Foresight's instructions for upgrading to 2.0 (or greater of) DBS-KAT or (2) install release 2.0 (or greater of) of DBS-KAT and rebuild from scratch a new DBS-KAT data base. Use the DBS-KAT order Use the DBS-KAT order _____________________ form (type: KAT -O to print it out) to order these two utility form (type: KAT -O to print it out) to order these two utility ______________________________________________________________ programs. Note: DBS-KAT registration entitles one to the database programs. Note: DBS-KAT registration entitles one to the database ___________________________________________________________________ utilities diskette. utilities diskette. ___________________ The DBS-KAT database is made up of four components: 1. The DBS-KAT database dictionary file, KATDB.DBD. It never changes and can be rebuilt by going back to the original file from your original (latest version) DBS-KAT diskette. DBS-KAT DATABASE INTEGRITY - Page 2 2. The DBS-KAT database key files, KATDB.KE? files. They can be rebuilt by running the KEYBUILD utility program (see below). There are four DBS-KAT key files: (a) one for each diskette volume ID, (b) one for each diskette filename entry, (c) one for each diskette-contained subdirectory name, and (d) one for the numeric ID DBS-KAT assigns for each diskette-contained subdirectory name. 3. The DBS-KAT set pointers, which are contained alongside each data record. The only DBS-KAT set is the diskette volume set, which has a parent record for each diskette cataloged and a zero-to-many number of child records for each parent record representing the number of filenames associated with that diskette. The set pointers for each child record are: (a) pointer to parent record, (b) pointer to prior sibling record, (c) pointer to next sibling record. The set pointers for each parent record are: (d) total number of children (not really a pointer), (e) pointer to first child (lowest alphabetical diskette filename), and (f) pointer to last child (highest alphabetical diskette filename). 4. The DBS-KAT end-user data, which is kept in the database in the form of data records. Alongside each database record, however, are set pointers (discussed previously). The built-in integrity checking of DBS-KAT's base system diskette only works the DBS-KAT keyfiles and the first type (a) set pointer. The majority of database damage will cause this built-in checking to spot it. Very rarely will a damaged database pass this built-in integrity checking for rarely is database damage solely limited to damaged set pointers, type (b) through (f). However, if the only database damage is missing entries in the DBS-KAT keyfile (b), the built-integrity checking of DBS-KAT will not detect this damage. Because very rare database damage can slip by the built-in integrity checking provided by the base system diskette of DBS-KAT, Applied Foresight Inc. provides the optional database utility diskette. Applied Foresight believes all users should get this diskette and is therefore making it available for only a small handling and mailing cost. The utility software is not ShareWare and is discussed in more detail below. Database damage can occur when: a. A user operates his computer under abnormal power conditions (undervoltages/overvoltages occurring). Tripp-Lite Manufacturing out of Chicago makes an affordable voltage regulator for $219 (retail), called the LC-1200. b. A user operates his computer under abnormal high static electricity. Buy just about any type of static electricity preventive device. c. Badly-behaving background memory programs are causing damage (none yet known to Applied Foresight's knowledge). d. The User's file directory is corrupt. (Run the DOS program, CHKDSK /F to see if your directory is corrupt. If it is, answer "Y" to the prompt. Rerun afterwards if an error is detected to see if the DBS-KAT DATABASE INTEGRITY - Page 3 /F (fix) option cleaned it up.) e. The database ends up sitting on a bad part of a user's disk drive. Norton's program, DISKTEST (or DT) may remedy this problem, as long as the bad file detected isn't a DBS-KAT database file. f. The user intentionally or unintentionally aborts out of an update function of DBS-KAT, and a user does not do the prescribed DBS-KAT recovery, as documented in the base system DBS-KAT Technical Reference manual. For example, the user midway through an update of a diskette discovers he has used the wrong volume number and presses CTRL-C or CTRL-BREAK. This can cause a corrupted database. Only exit the DBS-KAT update routines in a normal manner. g. The user is using a computer which has an unsynchronized operating system. That is, COMMAND.COM, IBMBIO.COM (IO.SYS on some clones), IBMDOS.COM (MSDOS.SYS on some clones), do not all belong to the same operating system. This situation develops when a user updates to a newer operating system by only using the DOS copy command. To see if your system is in synch, do the following: At the root directory of the drive you boot up on, type: KATSCAN *.* and press ENTER. As soon as the first three file entries appear, press the CTRL-BREAK key to abort the display. The first two filenames should have "SYS" appearing in the far right hand column of the KATSCAN display. The third filename should be COMMAND.COM. Do a SHIFT-PRTSC print-screen of this display. Repeat this procedure on your original DOS diskette. Compare the filesizes and dates to make sure everything compares ok. If the operating system is not in synch, perform the following steps to take the absolute safest steps to clean up your system. If you don't know how to do the below, consult either your computer manuals for more detailed instructions or a local computer dealer to help you do this. 1) Type: KATSCAN and press ENTER. Use "*.*" as the file set to scan and "P" for the redirection option. This will print out how your fixed disk is setup. Consult the KATSCAN operation documentation for more information. 2) Delete all old DOS programs from your disk drive. Use the DIR command against your DOS diskette to figure out what the filenames are. 3) Restart your computer using the DOS diskette that you want to upgrade or reinstall with. Make sure it has the write-enable notch taped over. Type: BACKUP C:\*.* A:/S and press ENTER. This will backup all non-DOS files on drive C:. Note: When prompted, remove DOS diskette and insert first formatted diskette which you will use to backup your computer. 4) Type: FDISK and press ENTER and choose the option to Remove DBS-KAT DATABASE INTEGRITY - Page 4 your DOS partition. Some manuals will tell you that all you have to do is use SYS: and COPY commands to update your operating system. This isn't always true, depending on the version of DOS and the brand. I have upgraded hundreds of computers and the method given here is the safest. 5) Turn off your computer, wait 1 minute. Put your new DOS diskette in drive A: and turn computer back on. 6) Type: FDISK and press ENTER and choose the option to Install DOS partition. Use the entire drive. 7) Type: FORMAT C:/S and press ENTER to format your hard disk as a bootable device. 8) Type: MD \DOS and press ENTER to create a directory to hold your DOS programs. 9) Type: COPY A:*.* C:\DOS /V and press ENTER to install all your original DOS programs to the \DOS directory. Afterwards, type: DEL C:\DOS\COMMAND.COM and press ENTER, to avoid duplicates. 10) Insert diskette 1 of your backup set in drive A:. Type: CD \DOS and press ENTER. Type: RESTORE A: C:\*.* /S/P and press ENTER. This will restore everthing that isn't already on the new setup drive C:. When prompted if you want to overwrite a file, answer "N". 11) Very important: verify that your CONFIG.SYS file has a line, FILES=20, in it. Type: TYPE C:\CONFIG.SYS and press ENTER. If it doesn't, reread DBS-KAT install instructions pertaining to CONFIG.SYS and AUTOEXEC.BAT. Note: Refer back to the DBS-KAT install instructions for Novice Users to make sure that your reinstalled \AUTOEXEC.BAT file complies with your new environment (ie, your old DOS files might not have been in a directory called \DOS). When you've verified that CONFIG.SYS is setup okay, remove all diskettes from drive A: and restart your computer. DO NOT SKIP THIS RESTART! h. The software which updates the database has a serious bug which can cause database integrity to be lost. HOWEVER, to the best of Applied Foresight's knowledge, there are no bugs in DBS-KAT software which can cause this type of damage, AND to the best of RAIMA Corporation's knowledge, there are no bugs in DB_VISTA 2.11 software which can cause database damage. DBS-KAT DATABASE INTEGRITY - Page 5 i. The DBS-KAT software program has become corrupted because of a poor file copy, bad disk drive, or corrupted file directory. Compare the DBS-KAT software on your fixed disk with your original DBS-KAT software diskette, using the DOS command COMP. Since DBS-KAT uses compressed programs, you would have to save your existing DBS-KAT programs (using the DOS COPY command) to a blank diskette, and reinstall the DBS-KAT programs (only the programs!). Afterwards, you'd type: COMP KAT*.EXE A: and press ENTER to compare the DBS- KAT programs on your fixed disk with those earlier copied to diskette prior to the reinstall. THE DBS-KAT(TM) DATABASE UTILITY PROGRAMS Use of the DBS-KAT utility diskette programs are provided under written license to Applied Foresight, Inc., by RAIMA Corporation. These programs, KEYBUILD and DBCHECK are not ShareWare programs and you are not authorized to distribute these programs to other persons. The written license allows Applied Foresight to distribute these diskettes to DBS-KAT owners who arrange with Applied Foresight, Inc., to receive them. Support for these two programs for DBS-KAT users is only through Applied Foresight, Inc. Do NOT CONTACT RAIMA Corporation for support. RAIMA Corporation only provides support for those customers who have PURCHASED a RAIMA product. Instructions for running these programs are supplied when one purchases the utility diskette from Applied Foresight. DATABASE CONSISTENCY CHECK UTILITY The DBCHECK database utility will perform the following consistency checks: For each data file (KATDB.DA*): - Validate each record's record id number and database address. This will ensure that no garbage data or bad records have been written to a data file. - For each key field contained in each record, verify that the key does indeed exist. For each key file (KATDB.KE*): - Verify the number of slots used in each node. This will also check for garbage data. - Read the record associated with each key and verify that the contents of the key data field matches that stored on the key file. All database consistency errors are printed to "stdout" and give the location of the offending key or record. KEY FILE BUILD UTILITY The utility KEYBUILD will rebuild all key files for the DBS-KAT DBS-KAT DATABASE INTEGRITY - Page 6 database. It rebuilds the key files by first initializing each key file and then scanning each record in each data file and reinserting all keys in the record. This utility can be used to recreate the key files when there's a database inconsistency (e.g. as reported by DBCHECK). SUMMARY The cautious user will purchase the DBS-KAT database integrity utility diskette and use the DBCHECK program 1-2 times a month to monitor the integrity of his database. If you discover with DBCHECK that you have a physically corrupt database, perform the following steps: 1. Run KEYBUILD to rebuild your database key files. 2. Run DBCHECK to see if the rebuilt database is clean. If it is, your recovery is finished. Backup this database and keep it around for awhile for safety sake. Attempt to ask yourself what might have caused the damage and learn from your analysis. 3. Continue if your database is still damaged. 4. Per the recovery instructions in the base system DBS-KAT Technical Reference manual, restore to your last good DBS-KAT database backup. (This includes getting a printout of your KATDB.LOG files of what diskettes have been processed since your last backup.) Run DBCHECK to see if the recovered database is clean. If it is, reprocess the diskettes entered since your last backup and then your recovery is finished. If your recovered database is damaged, then go to step 1 now. 5. If you can't restore to a prior DBS-KAT database which is good, you'll have to reinstall DBS-KAT from scratch and rebuild your DBS-KAT database from scratch. KATSCAN: The Hard Disk Archive Utility of DBS-KAT (R) by Applied Foresight, Inc. P.O. Box 20607 Bloomington, Minn. 55420 (C) Copyright 1986 R.H. Martin. All Rights Reserved. KATSCAN is a dual purpose utility program: * It is a stand-alone program for hard disk archiving which makes it easy for hard disk owners to manage & locate the files on their hard disk. * It has an undocumented function to support the cataloging functions of DBS-KAT, & for this purpose, it needs to be installed along with the other DBS-KAT software. KATSCAN can be prematurely aborted by pressing the ESC key. If that doesn't work, then try pressing the BREAK key while holding down the CTRL key. KATSCAN is for 320 KB RAM computers which have a hard disk & PC-DOS or MS-DOS 2.00 or greater. STAND-ALONE KATSCAN FEATURES KATSCAN can be ran identical to the DOS "DIR [file-search-string]" function. When so ran, it will: * list all selected files & in what directories they exist on the default hard disk. Note: KATSCAN, if ran this way, can only search the default disk drive. * provide a fileset size subtotal per directory & per drive. KATSCAN can be ran without any command line options & the user will be prompted with a variety of options to choose from. For each prompt, the user can take a shown default answer, or can type in an alternative answer. User is: * Prompted for drive to search. * Prompted for a DOS "DIR [file-search-string]. * Prompted if only files modified since last backup are to be selected. -> If "No" chosen, user is prompted if a date range is desired. - If the default ending date is not chosen, user is prompted if program files (.COM & .EXE) files are to be excluded. Since program files are not updated by end-users, if one is looking for obsolete end-user made files, one will typically not want programs to be included in a file cleanup search. * Prompted if output is to go to a file, console or printer. KATSCAN P. 2 -> If "File output" is chosen, user is: - Informed that an output DOS BATCH file, \KATCOPY.BAT, is made. When the program ends, if the user types: KATCOPY & presses ENTER, the files selected by the search will be copied to a specified target drive. - Prompted for the target drive letter; the number of KB that can fit on the target drive; & if only modified files are being searched, if the DOS BACKUP file attribute setting should be unmarked. + If the number chosen is 0, the target drive is assumed to have an unlimited KB size. + If the number chosen is greater than zero, when KATCOPY is ran, if it needs another diskette inserted, it will: o If desired, DBS-KAT will catalog the diskette (KAT -U1N command). o Prompt user to insert another formatted diskette. o Pause until the user presses any key. User should insert new diskette before pressing any key. o Perform a DIR /W against the newly inserted diskette. o Prompt the user "If not okay to delete all the shown files, either (1) answer "N" & continue with copying or (2) press CTRL-BREAK & abort now." This provides the user with a last chance to change his/her mind before continuing. If the user answers "N", the user should have chosen an output number small enough that the chosen files will have room to be added to the already existing files on the target diskette (assuming there are some). o Delete all the files in the current directory of the target drive (DEL *.*). When given the prompt "Are you sure (Y/N)?", the user can choose "Y" or "N" or CTRL-BREAK. - Prompted if one desires interactive authorization of each search-selected file. If answer is "Yes": + As the search selects each file, it will display the drive, directory location, filename, date, time & filesize. + User is prompted for each displayed filename, "OK to setup for COPY?". Chosen files won't be copied until the KATSCAN program ends, & the user types: KATCOPY & presses ENTER. - Prompted if one wants a delete-process batch file made of selected files. If the answer is "Yes": KATSCAN P. 3 + The created batch file name is \KATERASE.BAT. After the KATSCAN program ends, the user can execute this delete-process by typing: KATERASE & pressing ENTER. + User is prompted if one desires interactive authorization of each search-selected file. If answer is "Yes": o As the search selects each file, it will display the drive, directory location, filename, date, time & filesize. o User is prompted for each displayed filename, "OK to setup for DEL?". Chosen files won't be deleted until the KATSCAN program ends, & the user types: KATERASE & presses ENTER. o Answering "Yes" to both interactive authorization prompts provides user with the opportunity of having a different selection of files to copy than to delete. + At the end of the KATSCAN, the user is reminded that there is a KATCOPY batch command file to perform. + When the KATERASE process is actually executed, it will automatically delete itself when done. - Inform the user that the program will not select certain filenames. These are: + Filenames which contain the phrase "KATDB.", except KATDB.LOG. These are the DBS-KAT database files which are usually large & are best backed up from within the DBS-KAT program itself, so that the DBS-KAT program, KAT, can keep track of database backups. + The KATSCAN created files, \KATCOPY.BAT, \KATERASE.BAT, and \KATBACK.BAT. + Selected files whose size are greater than the user indicated maximum KB size are not included in the \KATCOPY.BAT file. o They are instead included in a DOS batch command file which can back these files up to the same target drive using the DOS BACKUP command. o The created command file is called \KATBACK.BAT. o At the end of the KATSCAN, the user is reminded that there is a KATBACK batch command file to perform. - Informs the user at the end of the KATSCAN, of how many formatted diskettes are needed to perform the KATCOPY process. -> If Console or Printer output is chosen: - Column headings will be printed once. Headings are: Filename, Size, Date, Time, Since Last B/U. KATSCAN P. 4 + The "Since Last B/U" column will be blank unless the corresponding file has been modified since the last DOS BACKUP. + Note, other backup programs may modify a DOS file attribute, such as FASTBACK. + Modified files will show the abbreviation "MOD" on the output display. + System files will show the abbreviation "SYS" on the output display. - Provide a fileset size subtotal per directory & per drive. - If console output is chosen, the user is displayed one screenful of output & the phrase "--More--". The program pauses until any key is pressed, at which time another screenful will be displayed. - If printer output is chosen, a formfeed is done at the end of the display. EVERYTHING DESCRIBED HERE IS ON THE ENCLOSED DISKETTE. THIS IS NOT DEMO SOFTWARE! THE DB-SHAREWARE PROGRAM by R.H. Martin Applied Foresight Inc. P.O. Box 20607 Bloomington, Minn. 55420 Jan. 1, 1989 Copyright 1986 by R.H. Martin All Rights Reserved Trademark Pending DB-SHAREWARE PROGRAM Copyright 1986 R.H. Martin P. 2 ABOUT DB-SHAREWARE SOFTWARE PRODUCTS ------------------------------------ OVERVIEW DB-SHAREWARE is a new and un-trademarked designation referring to a modified SHAREWARE product where the programmer has developed software revolving around a network model database, using a compiled language- driven, run-time royalty-free and license-free database manager. The DB-SHAREWARE designation was originally entitled "DB-SHARE", however Applied Foresight Inc. became aware of an advertisement in the April 1986 issue of DATA BASED ADVISOR that JCL Software has declared a trademark on a product, called "dBSHARE II". This trademark is close enough to cause confusion and to avoid this, the "DB-SHARE" concept is being renamed "DB- SHAREWARE". Although this makes the term similar to "SHAREWARE", since the "SHAREWARE" term is not trademarked and is meant to apply to any- body's offered software who follow the "SHAREWARE" concept, and the "DB- SHAREWARE" is a slight modification of this concept, the closeness is justified and there are no legal considerations to be concerned with. SHAREWARE is an untrademarked term used by Quicksoft (TM), the developer of PC-WRITE (TM). Write Quicksoft, 219 First N. #224, Seattle, WA 98109. Bob Wallace, the developer of PC-WRITE, describes SHAREWARE in his manual as follows: "Shareware is our term for software that can be freely copied and shared. The term (from an INFOWORLD column) describes both public domain (non-copyrighted) software, and copyrighted software, like PC- WRITE, which the author supports and encourages people to copy and share. "Shareware is like public television: the programming is freely dis- tributed, but support from users is encouraged. The concept is based on these principles: 1. People need to try programs to see if they are useful. 2. Software authors can be supported directly by users. 3. Copying and networking of programs can be encouraged. "To quote Andrew Fluegelman: 'This is an experiment in economics more than altruism. Free distribution of software and voluntary payment for its use would eliminate the need for money to be spent on market- ing, advertising, and copy protection schemes. Users could obtain quality software at reduced cost, while still supporting program authors.' "Quicksoft takes the Shareware concept further by giving additional materials and services when someone registers, and giving a commission to people who distribute copies." Anyone is allowed to sell or give away wholly unmodified copies of the official Shareware-release diskette. The "official" release is the one DB-SHAREWARE PROGRAM Copyright 1986 R.H. Martin P. 3 released by the software author. Shareware does not allow distribution of any modified software copies, nor source files, nor printed copies of the manual, without permission of the Shareware author. FEATURES DB-SHAREWARE differs slightly from the Shareware program. The main fea- tures of a DB-SHAREWARE software product are: 1. The software package revolves around a network model database, using a compiled programming language-driven, run-time royalty-free and license-free database manager. So far, only DB-VISTA by RAIMA Corpo- ration seems to fit this requirement. DB-VISTA is sold by RAIMA Cor- poration, 12201 SE Tenth St., Bellevue, WA 98005. RAIMA Corporation is NOT connected with Applied Foresight nor the DB-SHAREWARE program. One could justifiably include in the DB-SHAREWARE category, otherwise qualified software but instead of being a compiled programming lan- guage driven, run-time royalty-free database manager, alternative software using such royalty free database products as the CLIPPER and WORDTECH dBASE III royalty-free compilers. Likewise, substitute royalty-free sophisticated file-access systems, like BTRIEVE by SoftCraft, could be a component of a DB-SHAREWARE product, because intelligent use of key file access systems can make a program perform as if it was a program dependent on a network model database manager. 2. The base package is distributed similar to SHAREWARE. Parts of the code may be copyrighted software by the involved author and other parts may be public-domain coded subroutines. Due recognition is given to any public domain code utilized. Anyone is allowed to sell or freely give away wholly unmodified copies of the DB-SHAREWARE base software diskette. DB-SHAREWARE does not allow distribution of any modified software copies, nor source files, nor printed copies of the manual, without permission of the DB-SHAREWARE author. Policy about manual copying may vary amongst authors. 3. The base package must be completely useable and practical without the need for the optional (by purchase) add-on package. Those users who like the base package and want the luxury optional program features provided by the add-on package, can register with the software author and receive the add-on package and several other benefits. However, the base package must be good enough on its own merit to generate a widespread public enthusiasm for it and be able to sustain widespread copying and cheap or free distribution of it. The base package is NOT to be viewed as a demo software product. The add-on package provides only luxury features, not needed to functionally use the base package in a practical manner. 4. A DB-SHAREWARE add-on software diskette will only be distributed by the author or legally contracted distributors. A harmless, but gen- DB-SHAREWARE PROGRAM Copyright 1986 R.H. Martin P. 4 erally persuasive security measure will be used to prevent unauthorized distribution of a DB-SHAREWARE add-on software diskette. The diskette will contain in an encrypted manner, the customer's name and serial number, which will become encryptically embedded in any and all user databases which have the add-on program ran against it. Thereafter, everytime any base DB-SHAREWARE program or add-on DB- SHAREWARE program is ran against that user's database, the decrypted user's name will appear on the screen and printouts. DBS-KAT uses the following manner. ("XYZ" stands for the DB-SHAREWARE database name.) ********************************************************************* XYZ Database of: John Q. Owner S/N 99999999. ********************************************************************* Although, some unscrupulous persons may still copy an add-on DB- SHAREWARE program, they will have to put up with their computer screen and printouts advertising the fact that they are unscrupulous. Any known instances of copyright violations of a DB-SHAREWARE add-on program diskette should be reported to the software author. Some dishonest persons may order this year's upgrade add-on module and their friend might order next year's add-on module, and then both might share programs, except that one runs the other's programs in reverse order so that finally one's own name gets embedded in their individual's DB-SHAREWARE database. To disallow this, an add-on DB- SHAREWARE program will only re-update its embedded owner's name, if the add-on version number is newer than the last re-update embedding. 5. Each DB-SHAREWARE software author is independent of other DB- SHAREWARE software authors, unless specifically stated. The quality and reputation of each DB-SHAREWARE software product reflects only upon the responsible individual author. 6. DB-SHAREWARE add-on software will be minimally priced, rarely if ever going over a two digit price figure for any personal computer application. If the DB-SHAREWARE targed audience is small, a DB- SHAREWARE developer can sustain one's revenue needs through offering multiple, inxpensive add-on software modules for a base DB-SHAREWARE software product. 7. DB-SHAREWARE authors should have a conscientious committment to upgrade both the base DB-SHAREWARE and DB-SHAREWARE add-on software whenever feedback from users indicate that deficiencies exist. Any deficiency affecting functional use of the base package in a practi- cal manner, when resolved, should appear in the base DB-SHAREWARE product. PHILOSPHY Besides sharing the concepts behind SHAREWARE, DB-SHAREWARE has addi- tional concepts. Software products revolving around a compiled-language DB-SHAREWARE PROGRAM Copyright 1986 R.H. Martin P. 5 drive database manager are typically applications that are many faceted. There are the basic facets which critically maintain and use the applica- tion and there are numerous "peaches and cream" facets which make the use of the application even more worthwhile. A DB-SHAREWARE software developer knows that one's development effort will be financially rewarded if one has developed a base package that people love to use and copy, because anyone who uses the base package long enough will eventually want and will likely get the add-on software. However, the secret to a software developer's success is to make the base package highly desirably useful in its base state, because otherwise the initiative to enthuasiastically use it and share that enthusiasm through copying and sharing it with others will not be there. Without that enthusiasm over the base DB-SHAREWARE product, there will not be enough of a distribution spread and hence any derived registrations will be less than desired. The above formula is a "you win-I win" formula for both the developer and the customer. The customer gets a very useful base product free (or nearly free, if an intermediate distributor charges a handling fee) and is able to get add-on features direct from the developer, or an author- ized distributor, for minimal costs. The developer wins because a widespread enthusiasm of one's base product will naturally be followed by numerous registrations. The developer is protected from widespread copy- ing of the add-on diskettes, because of the security protection device. The honest customer is not hassled by the security protection, because infinite number of backup copies can be made, and the software employs no floppy-dependent mechanisms. Either party (user and author) is only going to win in this situation if the other party is allowed to win. Thus, the challenge goes out to future DB-SHAREWARE developers: "Don't put out anything but an excellent base product!" If the public's feedback to the base DB-SHAREWARE pro- duct is less than enthusiastic, improvements deserve to be put in the base DB-SHAREWARE product, not necessarily the DB-SHAREWARE add-on modules. LIMITATION OF DB-SHAREWARE COVERAGE Not all data base dependent software lends itself to the DB-SHAREWARE concept. Complicated software requiring accompanying audio visual train- ing material, and implementation or maintenance assistance by local con- sultants are two obvious types of software beyond the applicable range of the DB-SHAREWARE concept. Software easily able to be a success in a con- ventional commercial manner would be foolish to distribute in a DB- SHAREWARE manner. DB-SHAREWARE makes sense for those database dependent applications that are simple to use and which would be overpriced and undersold if sold via conventional methods. It also makes sense for cash-starved start-up com- panies. DB-SHAREWARE PROGRAM Copyright 1986 R.H. Martin P. 6